On Mo 7.Dez'09 at 20:08:12 +0100, Ralf Hoffmann wrote: > > The first one fixes a rare problem with "orphaned" windows. If a > window is opened only for a very short time and closed right away, in > some circumstances the frame around it keeps opened. It looks like > Window Maker doesn't get the destroy message. I have a small test > program for this but the problems depends on the speed of the > machine and is not easily reproduceable.
I never noticed this, could you share your test program just in case? > > So far about my patches. Now it's time to report a bug I noticed when > I was testing the current git version. The commit e4800e introduces a > problem with multi-screen setups. Each screen has an own default > visual so setting one "just for the case" will make Window Maker abort > because the default visual for screen 0 is not usable for screen 1. So > Window Maker doesn't start in my setup. The mentioned commit isn't > actually the problem, it's the whole single global wVisualID > variable. In its current state it's pretty useless in a multi-screen > environment and so is the command line argument --visual-id. > > I propose the following solution: There should be an array of > visualIDs and only the first one can get a default value (or the > default for each screen). The command line argument could be a comma > separated list of visuals to use. That should catch most use cases and > the default behavior without setting anything would work on > multi-screen setups and composite-enabled environments. I can create a > patch since it looks like I'm the only one working with multiple > screens. Sounds reasonable, and if it works for you than it is all fine I guess. Thanks for sharing your patches btw, even though I can't reproduce your problems. I uploaded your patches to the 'next' branch in case anybody else can test them (I folded some trivial style changes to your last patch). -- To unsubscribe, send mail to [email protected].
