Hello,
Ok, this subject is delicate ...
Examples of pb:
- Start Mozilla, say that its position is +x+y. Set fullscreen (F11),
if you have a not too recent version of Mozilla this works (with
Mozilla-1.4 and maybe other this does not work as Mozilla use
NET_WM_FULLSCREEN which is not implemented in fvwm (this not the point
of this email). Reset to normal state (F11). Then, either Mozilla
crash or the Mozilla window totally disappear (strange) or the new
window position is
+(x-"left_frame_width")+(y-"top_frame_height")
- Other Mozilla pbs: resizing the window with the internal Mozilla
resize grip.
- Tk experience:
[EMAIL PROTECTED] olivier]$ wish
% wm geometry . +0+0
The top-left part of the frame is out of screen
- This problem will happen with any QT, GTK, JAVA and Tk application
which "move-resize" itself (after mapping).
All this applications are not buggy! They all respect the ICCCM2 (or
at least a really reasonable interpretation of the ICCCM2). Note that
most of the actively developed window manager respect this (e.g.,
icewm, kwin and metacity). Also this is documented in the EWMH spec.
Of course fvwm no that, however it use a legacy way to move-resize
a window because some "old" apps use this legacy logic (sorry I've no
example, but Dominik has surely some).
I suggest that we add a new style:
LegacyConfigureRequest / ICCCMConfigureRequest
or
ICCCMConfigureRequest / LegacyConfigureRequest
to handle this problem. About default we can do something a bit more
complex: detect if the app respect the EWMH spec, if yes use
ICCCMConfigureRequest if not use LegacyConfigureRequest. However, I
think we need a new style (as there is no standard way to detect
that an application respect the EWMH spec).
Any opinions/comments/objections?
Regards, Olivier
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
