Rhialto <[email protected]> writes:
> It is probably the parsing of the config file, or applying it to the
> windows. When I was playing with it, I made thise extra entries to my
> .ctwmrc:
>
> this in one of my existing menus:
>
> "Priority" f.menu "OnTopPriority"
>
> and this extra menu:
>
> menu "OnTopPriority" {
> "+2" f.changepriority "+2"
> "+1" f.changepriority "+1"
> "-1" f.changepriority "-1"
> "-2" f.changepriority "-2"
> }
>
> and that at least should work (I just did a quick test). I could lift
> some windows on top of others, and see the resulting priority change via
> f.info.
>
I put that into my ctwmrc and now I can get the clock to stay on top,
just with +2.
