FVWM: How to bring FvwmIdent onto layer 6 [Was: FvwmIdent disappears very often]
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
Re: FVWM: How to bring FvwmIdent onto layer 6 [Was: FvwmIdent disappears very often]
On Mon, Jan 09, 2012 at 10:41:46PM +0100, 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".
Big man, he say "Woo, bright light in sky. Oog.", and the villagers, they
rejoice because it comforts them. "Oog, oog, oog." they prance around in
delight, whilst looking up at the bright light in the sky.
Unfortunately, this doesn't have anything to do with my original reply.
Unfortunately though, I've now conflated that with said reply, so you're
likely just as confused as I was when reading this.
Michael, if you've got two separate problems, please treat them as such. So
far, I've had to do the following:
* Wade through a plethora of FVWM config which isn't really related to your
problem most of the time, but gets included by you somehow because it's
easier. Fine, but my brain is tired of interpreting it all the time.
* Separate out in my head the different issues and decide if they're even
related.
* Still give meaningful replies to you based on observations you've had, but
which haven't been asked as questions by you, but actually form more
important information than anything you might have mentioned (difficult on
your part because if you knew this information you wouldn't have to ask
the questions in the first place, I know).
None of the information you've given above about vector buttons ever *made*
it in to your original email, and yet now they're conflated with
minimal_layers and God knows what else.
Separate them out, and ask separate questions, as many as you like in
different email threads if you so wish, but don't give me disparate pieces
of information like the above and expect me to be able to connect the dots.
It just won't work.
So, the above will need explaining -- because it makes no sense to me.
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
