Thomas Adam wrote: > On Fri, Jan 20, 2012 at 10:42:41PM +0100, Michael Großer wrote: >> # Bind some decors to the buttons at the left side >> ButtonStyle 1 - Clear MwmDecorMenu >> ButtonStyle 3 - Clear MwmDecorStick >> ButtonStyle 5 - Clear MwmDecorLayer 6 >> ButtonStyle 7 - Clear MwmDecorLayer 4 >> ButtonStyle 9 - Clear MwmDecorLayer 2 >> >> # Bind some decors to the buttons at the right side >> ButtonStyle 2 - Clear >> ButtonStyle 4 - Clear MwmDecorMax >> ButtonStyle 6 - Clear MwmDecorMin >> ButtonStyle 8 - Clear MwmDecorShade >> >> I made a screenshot to show them in real live. >> >> Button 5, 7 and 9 show me the layer of a respective window >> (and I can change the layer by klicking one of the buttons). > > Right. Can you provide a more minimal configuration for this including any > mouse bindings and style lines affecting how the decor is rendered. I note > here you're not using a decor which might explain some of your problems. > But again I can't reproduce this.
Is this config minimal enough for you? http://www.jumping-blue-turtle.com/fvwm/will_disappear_on_random_date_2012-05-12/8998_bugdemo_002.tar.bz2 I tested it on FVWM "version 2.5.26". Press Win+x to get an "xterm". Press Win+n to get an "nedit" window. Press Win+f to get a "firefox". Other shortcuts are in "0005_general_shortcuts". At the bottom of the screen, you should find an FvwmIconMan. Rightclick with your mouse on an entry there. An FvwmIdent appears with button 7 pointed out: A continuous line indicates that FvwmIdent is in layer 4, but this is not true, because FvwmIdent is in layer 6. Move your mouse. As soon as another window gets focus, something at FvwmIdent will change: Now, button 5 will be pointed out: A continuous line indicates that FvwmIdent is in layer 6, which indeed is true. The bug is that FvwmIdent does not immediately indicate that it is in layer 6. The file "0001_window_decorations" contains the code that draws the buttons to the windows and colorizes the window decorations. I made the second and the third line of "0012_FvwmIdent" inactive. Normally, I need them active to fix some problems of FvwmIdent. When they are active, FvwmIdent always indicates the truth (the right layer). If you can reproduce this bug only with an older version of FVWM but not with a current version, then the case should be closed. If a current version also has this bug, then you can do something if you want. You also can wait some weeks until I test it against a current version by myself :-)
