bwhmather / wmii

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

Wmii fails to "activate" some windows #237

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Steps to reproduce:
1. start gvim
2. open a terminal and issue the command xdotool search --classname gvim 
windowactivate
3. You should see the error: XGetWindowProperty[_NET_WM_DESKTOP] failed (code=1)

I've tried with wmctrl -xa gvim as well, but it doesnt work.
The xdotool command works with Firefox though:
xdotool search --classname Navigator windowactivate
It switches to the tag where Firefox is located and switches to that client.

I'm using a program called Kupfer (http://kaizer.se/wiki/kupfer/), which is a 
launcher. When using the window actication in Kupfer it seems to work always. 
As far as I can tell Kupfer uses the python keybindings for wnck to activate 
the windows.

I'm running wmii-hg2786, ©2010 Kris Maglione on
Linux arch 2.6.38-ARCH #1 SMP PREEMPT Mon May 23 22:02:08 CEST 2011 x86_64 
Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux

Original issue reported on code.google.com by peterbjo...@gmail.com on 4 Jun 2011 at 8:32

GoogleCodeExporter commented 9 years ago
Hmm, I didn't think it was wmii's job to focus a client on its first view.  I 
always scripted this myself, instead, by offering a list of all clients in 
dmenu/wimenu and then taking the user's choice and (1) focusing the first view 
on which that client appears and (2) focusing that client.

Original comment by sun...@gmail.com on 19 Sep 2011 at 7:54

GoogleCodeExporter commented 9 years ago
wmctrl sends the request with an unknown source, which wmii 
ignores. Pager requests (which presumably xdotool sends) are 
always acknowledged. Client requests are only acknowledged for 
clients with activate permissions in their ctl files.

Original comment by maglion...@gmail.com on 19 Sep 2011 at 8:07