On 28 May 2002 20:11:37 -0500, Dave Trollope wrote: > > > > I have for quite sometime been wondering why on my system the > > > FvwmIconMan background was getting left corrupted when another window > > > was put on top of it, and then removed. Here is a patch. > > > > > > The problem was that between 1.4.5 and now, an if() in draw_manager() > > > was removed and the clear_empty_region() was (I think) moved. However it > > > was moved to an if() with different conditions - it used to be called > > > because numWindows > 0 (almost always) but this was no longer true. > > > > > > So, when an Expose event was received, the draw_managers was called and > > > the clear_empty_region() was never called. So I added to the dirty_flags > > > a REDRAW_BG flag, and set it from within man_exposed. This triggers the > > > redrawing of the background for the expose events. > > > > > > Please take a look at the patch and include it in the next build. > > > > Hm, wasn't that already fixed? For which release is that patch? > > 2.4.x or 2.5.x? > > Hi Dominik, > > I was setup for the latest code in cvs, 2.5.2 is what fvwm -v shows. > > I've seen this behaviour ever since 2.4.5, never seen it fixed since I've been > on the ML. > > I'm thinking perhaps I should regenerate the patch, I realised just now I put > the #define in the wrong set of defines. It doesn't cause a problem but the > correct place is a few lines down. I will re-issue the patch - especially > since I see others have added patches in the last few days too.
Dominik already applied your patch, probably on accident. Regards, Mikhael. -- 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]
