Thomas Adam wrote: > On Fri, Jan 20, 2012 at 09:37:07PM +0100, Michael Großer wrote: >> Michael Großer wrote: >> > When I only set "*FvwmIdent: MinimalLayer 6" without >> > the Style commands, though the FvwmIdent window >> > appears on layer 6, but the vector buttons in the window >> > decorations, wich I draw with ButtonStyle in my >> > "0001_window_decorations" config file, do not >> > get refreshed. They will get refreshed when I focus >> > another window. Setting the styles I need anyway >> > (StaysOnTop + NeverFocus) prevents this sort of laziness >> > of the vector buttons. This is a bug I know for months, >> > and I use "Stick" "Stick" to work around this. >> > Since I have a workaround, I would classify this >> > bug as "it would be nice if someone would fix it". >> >> I discovered the "Refresh" function today :-) > > No, you still didn't answer my question. I still don't understand why you > need Refresh here,
I have these 9 title-bar buttons: # 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). When I write > *FvwmIdent: MinimalLayer 6 into my config, then FVWM brings FvwmIdent onto layer 6, but the buttons do not always indicate that FvwmIdent is on layer 6. Sometimes, layer 4 or both layer 4 and layer 6 are optically latched. The reality may be OK, but the visual effect is not OK. When I use StaysOnTop and NeverFocus, then also the visual effect is Ok. I suppose that the "Refresh" function was invented for this kind of trouble. I don't know how a current FVWM version reacts, I'm still too impatient and use FVWM 2.5.26 instead of using a new version, because the other to-do list is long and using a current version of FVWM is somewhere in the middle of the other to-do list, where I go a clean way and take one thing at a time. Question answered? >> > Note: There are many commands that affect look and >> > feel of specific, some or all windows, like Style, >> > Mouse, Colorset, TitleStyle and many others. For >> > performance reasons such changes are not applied >> > immediately but only when fvwm is idle, i.e. no user >> > interaction or module input is pending. Specifically, >> > new Style options that are set in a function are not >> > applied until after the function has completed. This >> > can sometimes lead to unwanted effects. >> > >> > To force that all pending changes are applied >> > immediately, use the UpdateStyles, Refresh or >> > RefreshWindow commands. >> >> Nice Feature :-) > > But not needed anymore. I wouldn't confuse the two. Which "two" do you meam? Today, I solved a problem using "Refresh" during my attempts to build a KDE3 like alt-tab behaviour. If it is superfluous in later FVWM versions, I can still omit it in the future, but today, I needed it.
<<inline: layers.png>>
