search

erase-hup / autokey

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

shortcuts won't work until first launched command window is closed #191

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. create a new shortcut that opens another application (i.e.: 
system.exec_command("gnome-terminal")
2. launch the command
3. try to launch any other command through its keyboard shortcut

What is the expected output? What do you see instead?
until the previous window is opened, any other shortcut won't work... command 
will launch fine through panel icon. shouldn't i expect autokey to launch a new 
gnome-terminal window everytime the shortcut is pressed?

What version of the product are you using? On what operating system?
AutoKey (GTK UI) 0.71.0 on ubuntu 10.10

Original issue reported on code.google.com by masav...@gmail.com on 3 Apr 2012 at 7:49

GoogleCodeExporter commented 9 years ago 
correction:
the issue only affects scripts with the "midori" command...
substituted midori with firefox and now everything goes fine... :)

Original comment by masav...@gmail.com on 3 Apr 2012 at 4:37

GoogleCodeExporter commented 9 years ago 
This is more a case of user error... if you use a hotkey to start a program 
that will run for a long time, e.g. gnome-terminal or midori, you should use 
e.g.
system.exec_command('midori', False)
This will prevent AutoKey from waiting for the output of the command which 
prevents other hotkeys from being triggered (in the old version you are using). 
This problem does not exist at all in the latest version.

Original comment by cdekter on 4 Apr 2012 at 11:35