DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2039 Version: 1.3-current I understand the patch, and I think that it's okay as far as it does what the OP (kub) wants to achieve. kub wrote: "In the context of a resize with no new area covered, Xlib does not need to send the expose event as no new area is to be redrawn." Yes, that's okay, and I understand. But then: "In case of FLTK widgets this is a wrong assumption." Why? I'd like to understand and replicate the problem before applying a patch that would otherwise (maybe) result in too much drawing (slowing down the X server connection) for other WM's. So, what exactly are you doing, and why is the assumption wrong? AFAICT there must be a resize() involved that is in fact a shrinking of the window - after the window has been shown. Are there other widgets in the window that are resized, but are not drawn correctly? Questions to the OP (kub): - what are the effects that you see? - can you post a small example program that shows the effect? - is this still a problem, or is it maybe fixed otherwise (new FVWM version)? - is it only visible with FVWM ? Link: http://www.fltk.org/str.php?L2039 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
