Yes, xprop shows " Client accepts input or input focus: True" for both pane=
l and pinboard. Maybe it's the fault of this old ROX version? Is OroboROX=
denying focus on desktop and dock type windows?
regarding the client cycle bug, why did you change the code in the first pl=
ace? It was working without any problems in the last release.
I also wonder why you still don't accept my patch that ignores mouseclicks =
on unfocused windows when click-to-focus mode is used. If the only portio=
n of the window you want to focus/raise contains a button, you can't focu=
s/raise the window without clicking the button if you only use the mouse.
regarding multiple windows having focus at the same time, and no window hav=
ing focus at all, these things I have never had any problems with before =
this, but now it happens all the time, if I just change workspace then no=
window has the focus (not the top-most nor the one under the mousepointe=
r), and if I use client-cycle to get focus to window, all other windows a=
re still drawn as if they were focused.
PS. Forget me for the ugly quote style, I'm using my bad webmail shit as my=
real computer is dead.
From: Guido Schimmels <__guido__@...>
Date: Wed, 27 Jul 2005 14:40:08 +0200
Subject: Re: [rox-devel] [ANN] OroboROX 0.9.7
On Tue, 26 Jul 2005 20:48:36 +0200
"Kymatica" <than@...> wrote:
> OroboROX 0.9.7 bugs I found so far:
> when window is placed below (right clicking title-bar or while holding wi=
nops-modifier) the window is unfocused (it shouldn't be) - and no other w=
indow is focused instead unless there is another window that now gets und=
er the pointer (in focus follows mouse) in case that window is focused (w=
hich is the right thing).
> shadebutton on titlebar has no special cursor
> (maybe there should be an option to turn those fancy cursors off in case =
the user doesn't like them?)
> clientcycle is not working, windows are not unfocused=20
> and it cycles trough rox-filers pinboard and panel.
> pointing the mouse at the rox-panel steals the focus from windows.
> NOTE: This is only tested with ROX 2.1.3 as this is my old computer. (my =
new one has dies of unknown causes)
> Maybe the panel/pinboard stuff behaves different with newer versions of R=
Does xprop show "Input Focus True" or WM_TAKE_FOCUS?
I can not remember such a bug (which it clearly had been) anymore.
In this case I guess I have to reinstate the compatibility code, though don=
the idea having to do this class matching for every new window.
The other bugs you reported I have fixed.
There is one cycle bug left though. It gets stuck when it runs into a iconi=
It gets raised, then when you switch to the next, you see how it gets iconf=
raised and focused immediately again, and then this goes on for ever.
- K Y M A T I C A -