tendays
October 13th, 2007, 01:38 PM
Another thing:
I am using Ctrl-F1, -F2, etc to navigate workspaces.
Two minor bugs I'd like to report. Nothing too serious but I thought I should make devs aware of them.
First, I selected the "focus follow mouse" policy (i.e. I haven't selected the "click to focus" option in "Focus and Raise Behaviour").
I believe that, when changing workspace, the topmost window which happens to be under the mouse pointer should get selected, but that's not what happens. For instance if I have a sticky window (1) focused, then switch to a workspace that has a fullscreen window (2) covering that window 1, the sticky window (1) remains selected, although 2 should be focused instead. Second example:
1. I have a workspace containing two (non-sticky) windows 3 (on the left half) and 4 (on the right half).
2. I move the pointer over 3 to focus it.
3. Switch to another workspace.
4. Move the mouse to the right half
4. Switch back to the workspace containing 3 and 4.
Now the mouse is over 4 but 3 remains selected.
Second issue
As I said I'm using Ctrl-Fn to switch workspaces. The issue I'd like to report here is that the "Ctrl key released" event is sent to the selected window (which is annoying for instance if that window happens to be konqueror because it activates the link keyboard shortcuts).
Is that the expected behaviour? I thought that whenever a key combo is used by the window manager, it should not reach the applications. Compare for instance alt-click-dragging a window: We can see that the "alt key released" event doesn't reach the application because it doesn't active the menu navigation mode.
Thanks!
(My system:
tendays@badiane:~ $ compiz.real --version
compiz 0.5.3
tendays@badiane:~ $ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.04
DISTRIB_CODENAME=feisty
DISTRIB_DESCRIPTION="Ubuntu 7.04")
I am using Ctrl-F1, -F2, etc to navigate workspaces.
Two minor bugs I'd like to report. Nothing too serious but I thought I should make devs aware of them.
First, I selected the "focus follow mouse" policy (i.e. I haven't selected the "click to focus" option in "Focus and Raise Behaviour").
I believe that, when changing workspace, the topmost window which happens to be under the mouse pointer should get selected, but that's not what happens. For instance if I have a sticky window (1) focused, then switch to a workspace that has a fullscreen window (2) covering that window 1, the sticky window (1) remains selected, although 2 should be focused instead. Second example:
1. I have a workspace containing two (non-sticky) windows 3 (on the left half) and 4 (on the right half).
2. I move the pointer over 3 to focus it.
3. Switch to another workspace.
4. Move the mouse to the right half
4. Switch back to the workspace containing 3 and 4.
Now the mouse is over 4 but 3 remains selected.
Second issue
As I said I'm using Ctrl-Fn to switch workspaces. The issue I'd like to report here is that the "Ctrl key released" event is sent to the selected window (which is annoying for instance if that window happens to be konqueror because it activates the link keyboard shortcuts).
Is that the expected behaviour? I thought that whenever a key combo is used by the window manager, it should not reach the applications. Compare for instance alt-click-dragging a window: We can see that the "alt key released" event doesn't reach the application because it doesn't active the menu navigation mode.
Thanks!
(My system:
tendays@badiane:~ $ compiz.real --version
compiz 0.5.3
tendays@badiane:~ $ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.04
DISTRIB_CODENAME=feisty
DISTRIB_DESCRIPTION="Ubuntu 7.04")