Hi! There are two questions in one e-mail message. I have to split it and answer the questions separately.
Thomas Adam wrote: > s/minimal_layer/MinimalLayer/ Thomas Adam wrote: > On Fri, Jan 06, 2012 at 12:02:47AM +0100, Michael Großer wrote: >> Thomas Adam wrote: >> > On Thu, Jan 05, 2012 at 10:43:23PM +0100, Michael Großer wrote: >> >> When I additionally I set a StaysOnTop style to bring FvwmIdent on top, >> >> I noticed that this does only work when I apply FvwmIdent on >> >> xterms, but not on nedit, Iceweasel, FvwmIdent or some other instances. >> > >> > Look at the "MinimalLayer" option in "man FvwmIdent". Everything else >> > you've tried can be got rid of with this option. >> >> I tried it just now, and it does not reliably work. Not with my >> productive system (fvwm 2.5.26). I could try it again later when >> I migrate to something newer. > > Not reliably how? Here: > > *FvwmIdent: minimal_layer 10 > > Always puts FvwmIdent in layer 10 which is high enough to ensure it's not > obscured by any other applications. So, since you gave me a code snipped, I noticed now that I made a mistake. I confused the configuration options of FvwmIdent with the generic "Style" command of FVWM. My first attempt was: > DestroyStyle FvwmIdent > Style FvwmIdent StaysOnTop, NeverFocus, MinimalLayer 6 This could not work, because there is no style option called MinimalLayer. Now, my code looks like this: > DestroyStyle FvwmIdent > Style FvwmIdent StaysOnTop, NeverFocus > > *FvwmIdent: MinimalLayer 6 This works perfectly. Well, it only works perfectly, because I combine "*FvwmIdent: MinimalLayer 6" with "DestroyStyle FvwmIdent" and "Style FvwmIdent StaysOnTop, NeverFocus". 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". > What else in your productive system isn't working? My free hour for today is over. I think, the smartest approach how to answer this important question is that I make a list in which I mention all problems I'm confronted with using few words for each problem. Then I should prioritise all list entries in a way that the problems whose solution would bring me the most benefit are at the top of the list. I will do it during the next days. Thank you and best regards, Michael
