search

timoc / autokey

Automatically exported from code.google.com/p/autokey
GNU General Public License v3.0
0 stars 1 forks source link

Unable to set Window Filter #228

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. select an item
2. click "Set" for a Window Filter
3. type in a filter and click "Ok"

What is the expected output?
The Window Filter is set.

What do you see instead?
The Window Filter remains as "(None configured)"

What version of the product are you using? On what operating system?
autokey-gtk 0.90.1
Debian GNU/Linux wheezy/sid

Please provide any additional information below.

Here's the output of autokey-gtk -l during these operations:

2012-11-12 14:17:16,358 DEBUG - service - Window visible title: u'Set Window 
Filter', Window class: 'autokey-gtk.Autokey-gtk'
2012-11-12 14:17:16,358 DEBUG - service - No phrase/script matched hotkey
2012-11-12 14:17:16,881 DEBUG - iomediator - <super> released
2012-11-12 14:17:18,239 DEBUG - service - Received mouse click - resetting 
buffer
2012-11-12 14:17:19,788 DEBUG - service - Received mouse click - resetting 
buffer
2012-11-12 14:17:21,786 DEBUG - service - Received mouse click - resetting 
buffer
2012-11-12 14:17:30,439 DEBUG - service - Received mouse click - resetting 
buffer
2012-11-12 14:17:46,150 DEBUG - service - Received mouse click - resetting 
buffer

Original issue reported on code.google.com by pivanov...@gmail.com on 12 Nov 2012 at 11:47

GoogleCodeExporter commented 9 years ago 
I am experiencing the same thing with Linux Mint 14, autokey-gtk 0.90.1

Previously I set window filters and they worked.  They are still there.  I just 
tried to add a new rule with a new filter and although I enter the information 
(and it is there if I press set again immediately) the Window Filter line shows 
(None Configured) and it has no effect.

Original comment by mjohnly...@gmail.com on 4 Dec 2012 at 8:37

GoogleCodeExporter commented 9 years ago 
After thinking about this (and the logical way you structured your program) I 
looked for the files controlling the program.

I was able to edit the .json in ~/.config/autokey/data/Hotkeys and put the 
window filter in - who needs a gui :)

For pivanov, if you havent figured this out you can do it by changing the 
filter to match the regex you need:

    "filter": {
        "regex": ".* - Shutter", 
        "isRecursive": false
    }, 

John

Original comment by mjohnly...@gmail.com on 4 Dec 2012 at 8:55

GoogleCodeExporter commented 9 years ago 
This is not working for me, unfortunately. I tried setting:

"filter": {
        "regex": "^((?!.*Emacs).)*$", 
        "isRecursive": false
    }, 

to avoid AutoKey changing my Emacs keybindings, but it doesn't work. 
Unfortunately, without this feature the app is unusable to me. A shame, because 
I find it very powerful!

Original comment by kermit666 on 12 Jul 2013 at 7:36

GoogleCodeExporter commented 9 years ago 
OK, I got closer to the goal by using the scripting API (very nice 
capabilities). You can take a look at my code at

https://github.com/kermit666/dotfiles/tree/master/autokey

The most important script is combo.py

https://github.com/kermit666/dotfiles/blob/master/autokey/combo.py

which basically detects if I'm in an application where I want to disable 
Autokey and in that case does nothing.

Now my problem is that AutoKey seems to steal the key-combo anyway, so even if 
I don't cast any "wrong" output, the next application won't get to detect the 
key-combo. Is there any command to forward it further on?

Original comment by kermit666 on 12 Jul 2013 at 10:42

GoogleCodeExporter commented 9 years ago 
Thanks @John for the workaround I have the same problem with the gui not saving 
window filters anymore (worked fine before) - after restarting Autokey (it 
prompted me) the window filter showed up and worked fine. 

I am using Xfce on Ubuntu 13.04 if that makes any difference.

Tom

Original comment by tomjugg...@gmail.com on 6 Aug 2013 at 9:44

GoogleCodeExporter commented 9 years ago 
I too have this issue, running awesome-wm under a gnome-session in Ubuntu 
13.04. Like the above poster, my log didn't indicate that autokey even took the 
input of setting the window filter for the phrase.

Original comment by Rev.A.R....@gmail.com on 22 Sep 2013 at 5:32