Stefan Monnier <[email protected]> writes:
>>> This directive hasn't worked for me. I see in the docs that it might
>>> not always work. But it never works.
>> See if it works in 3.8.2. The OTP stuff came in since then and redid
>> how AlwaysOnTop and friends work, so maybe there's something in there
>> that's affecting it.
>
> Could be, indeed. I just noticed that my ~/.ctwmrc doesn't use
> AlwaysOnTop but uses OnTopPriority instead:
>
> OnTopPriority 7
> {
> "Sculptor" "Ipaste"
> "xine Video Fullscreen Window" "FULLSCREEN"
> }
>
> so indeed, my own setup doesn't test AlwaysOnTop.
> So, you an try replacing "AlwaysOnTop" with "OnTopPriority 7" (you can
> use another number between 1-7, of course, and it should give the same
> result).
>
> But another possibility is simply that the name is "wrong". I noticed
> that over the years, I sometimes have to tweak the name, so you might
> like to try with "XClock" (tho I just tried f.identify on an `xclock`
> window, and it seems to indicate that "xclock" should work for it).
>
>
OK I switched back to v4 and tried:
OnTopPriority 8 {
"XClock"
}
Also 7, and xclock in lowercase. But none of these worked. I see from
info that the "OnTopPriority" value is zero.
A footnote about "AlwaysOnTop", with 3.8 it was working, except for
when, using Seamonkey, I selected the Window option of Seamonkeys menu
bar to go from mail to web, or from web to mail. Then the xclock
disappeared. So I expect that is one of the occasions when it doesn't
work.
As a work around I might put a clock on my desk. A real one. :)
