On Mon, Feb 10, 2003 at 02:52:40PM -0500, Dan Espen wrote: > Isaque Galdino de Araujo <[EMAIL PROTECTED]> writes: > > On Mon, 10 Feb 2003 12:59:12 -0200 Isaque Galdino de Araujo wrote: > > > > > On Fri, 07 Feb 2003 08:26:17 -0500 Dan Espen wrote: > > > > > > > If you're not working from source, you might want to forward this to > > > > the fltk developers. > > > I'll do that. Thank you! > > > > Dan, I've sent to the fltk development people, what you suggested, and this i > > s what they send me back: > > > > --- cut here --- > > isaque at uol dot com dot br wrote: > > > ... > > > An application is supposed to redraw itself when it recieves a > > > ConfigureNotify event. Fvwm is sending the ConfigureNotify, but > > > fltk purposely doesn't redraw itself when it gets that event, > > > it waits for an expose event instead. > > > ... > > > > Actually, I checked the Xlib Programming Manual and the > > documentation on ConfigureNotify seems to indicate that the > > application should only force/perform a redraw for Expose and > > GraphicsExpose events - ConfigureNotify ONLY specifies that the > > window has been resized. From page 75: > > > > The ConfigureNotify branch, in all applications, will calculate > > the values of variables based on the new window size. These > > variable values will then be used to calculate where to draw > > things in the Expose branch the next time an Expose event > > occurs. A ConfigureNotify event is always followed by one or > > more Expose events. > > > > Note the last sentence, which is supported in other sections of > > the same manual... > > > > So either fvwm or X server is at fault for not following the X11 > > specification, and given that only fvwm seems to exibit this > > problem, it is likely a fvwm bug. > > > > Setting the redraw() flag but not waiting for an expose could cause > > unnecessary redraws on compliant window managers, so I'm not inclined > > to add this "fix" to FLTK... > > > > -- > > ______________________________________________________________________ > > Michael Sweet, Easy Software Products mike at easysw dot com > > Printing Software for UNIX http://www.easysw.com > > > Hmm, I'm bcc'ing Michael since I see he took pains to hide his > email address. > > Check out this xfree man page: > > http://www.xfree86.org/4.2.0/XResizeWindow.3.html > > That indicates that the expose events come from the X server. > BUT, it also says that the expose events are optional. > > I don't know what I can do to Fvwm to force the X server to > generate the expose events that fltk wants.
You can do nothing. Expose events are generated when parts of a window are *exposed*, not when they are covered. Applications that need to redraw when the window is shrunk have to react to the ConfigureNotify. > You might call this an X server problem, but I'm not sure they > will accept this as a problem since what the server is doing is > consistent with the man page. No, it's not an X server problem. It's simply a bug in the application. Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
