Peter Funk <pf_at_artcom0.north.de> writes:
> I've some applications, which store the window locations from previous
> invocations in the same manner. Whenever such an application program
> creates a window using the x,y-coordinates remembered from the previous
> run, the new window is moved right and down about the framewidth
> resp. framewidth + titlebar height. This does not happen with mwm,
> SGIs 4Dwm or Solaris ol(v)wms.
>
> fvwm seems to use the x,y-coordinates delivered to XCreateWindow for
> upper left corner of the frame window and not the pane window as
> other window managers happen to do. So the pane window get's
> increased x,y coordinates for each new run of the application.
>
> I've looked into fvwm-1.24r/fvwm/placement.c and this behaviour seems to be
> intended by the author. There is the following comment line near the
> end of the function 'PlaceWindow':
> /* put it where asked, mod title bar */
well one would want a window with -geom +0+0 to be placed at 0/0
(border edge!!!)
That means that the application pane has to be at
Borderwidth/Titleheight. If that is stored, that's a problem.
I always had the maybe related problem with 1.24, that my emacs is placed
slightly off-screen :
I had to specify (left . -7) (top . 23) as the geometry values for
emacs to get it in the top right corner.
I'm glad this was corrected in 2.xx (can't remember, but it's gone now.)
(identify says the geometry is +551-90, grrrrr)
anayway there's also that odd bug that -0-0 isn't done right
(i.e: first converted to integer, so the "-" is lost resulting in 0/0
placement).
maybe these two could be taken care of together ?
regards,
albrecht
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Apr 26 1996 - 15:08:24 BST