jerluc / wmii

Automatically exported from code.google.com/p/wmii
MIT License
0 stars 0 forks source link

XRandR: wimenu does not follow focus #79

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Have two screens with clients on both screens
2. Move the mouse to the other screen or focus a window on the other screen
with the Keyboard (Mod-Direction)
3. Type Mod-p or Mod-a, anything that spawns a wimenu

What is the expected output? What do you see instead?
I expect the menu to show up on the screen in which the currently focused
window is. What I see is that the menu still spawns on the other screen.

What version of the product are you using (wmii -v)? On what operating system?
hg2402 on Arch Linux

Please provide any additional information below.
Clicking with the mouse does shift the focus to the other screen. But this
is confusing because no clicking is needed to focus a window, while it is
needed to focus the screen.

Original issue reported on code.google.com by skwi...@googlemail.com on 23 Oct 2008 at 7:50

GoogleCodeExporter commented 9 years ago
The menu actually spawns on whichever screen the mouse is on, for the moment.

Original comment by maglion...@gmail.com on 14 Nov 2008 at 8:46

GoogleCodeExporter commented 9 years ago
For me the menu spawns on the screen that has last been clicked on, which is not
necessarily the screen the mouse is currently on.

Original comment by skwi...@googlemail.com on 19 Nov 2008 at 7:21

GoogleCodeExporter commented 9 years ago
Are you talking about Xinerama screens or two separate screens? The behavior is
undefined in the latter case. In the former, wimenu queries the pointer 
location,
finds which Xinerama screen it's in, and maps itself there.

Original comment by maglion...@gmail.com on 19 Nov 2008 at 7:50

GoogleCodeExporter commented 9 years ago
I am using XRandR screens.

Original comment by skwi...@googlemail.com on 20 Nov 2008 at 11:11

GoogleCodeExporter commented 9 years ago
This works for me now. Please mark as fixed.

Original comment by skwi...@googlemail.com on 23 Jan 2009 at 12:24

GoogleCodeExporter commented 9 years ago

Original comment by sun...@gmail.com on 22 Feb 2011 at 9:27