search

QiangF / autokey

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

Super key does not work for any hotkeys #7

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a new simple phrase in autokey
2. Set the hotkey to "Super" + x  (any letter key)
3. Save it.

What is the expected output? What do you see instead?

I'm expecting to output the phrase when my "Windows Key + x" is triggered,
but nothing happens.

If I change it to "Control + Alt + x" it will work. (More work than I'd
like though...)

However, I am using "Windows Key + t" in Gnome to open my terminal program.
In KDE I use "Input Actions" and have several combos with the winkey that
work fine.

What version of the product are you using? On what operating system?

Ubuntu 9.10 w/ Autokey 0.54.5-1 in Gnome

Please provide any additional information below.

Original issue reported on code.google.com by Shizit.H...@gmail.com on 13 Nov 2009 at 8:25

GoogleCodeExporter commented 9 years ago 
Please try with the latest version from the PPA.

Original comment by cdekter on 24 Mar 2010 at 11:23

GoogleCodeExporter commented 9 years ago 
I tried with 0.61.7 and the bug remains.

When I look at xev, it shows that the key is mapped properly:

KeyRelease event, serial 33, synthetic NO, window 0x6000001,
    root 0x10a, subw 0x0, time 13125347, (299,168), root:(307,265),
    state 0x20, keycode 133 (keysym 0xffe7, Meta_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

I've been able to launch my terminal using a windows key shortcut ("Mod3+T") I
assigned in "System -> Keyboard Shortcuts -> Run Terminal" under Gnome.

If there's anything I can do to help just let me know.

Original comment by Shizit.H...@gmail.com on 31 Mar 2010 at 10:46

GoogleCodeExporter commented 9 years ago 
What keyboard layout are you using? Do you use any hotkey-based layout
switching/group switching?

This type of issue is invariably caused by a disagreement between X and the 
rest of
the DE about what the real keymap is. AutoKey only asks X for the keymap - if X 
is
confused, there is nothing AutoKey can do about it.

Original comment by cdekter on 31 Mar 2010 at 10:49

GoogleCodeExporter commented 9 years ago 
BTW, I also tried mapping it to "Super_L" but that doesn't seem to work either:

xmodmap -e "clear mod3"
xmodmap -e "keycode 133 = Super_L"
xmodmap -e "add mod3 = Super_L"

KeyRelease event, serial 33, synthetic NO, window 0x6000001,
    root 0x10a, subw 0x0, time 14124395, (493,150), root:(505,271),
    state 0x20, keycode 133 (keysym 0xffeb, Super_L), same_screen YES,
    XKeysymToKeycode returns keycode: 115
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

Still doesn't work :(

Any ideas? I think it could be my keyboard config.

Original comment by Shizit.H...@gmail.com on 31 Mar 2010 at 10:58

GoogleCodeExporter commented 9 years ago 
AHA! I restarted gnome (without rebooting) and it is almost working now.

I say "almost" because if I set a hotkey "Win+X" to output "foobar", what 
happens is
it includes the "X". i.e: pressing "Win+X" will output "xfoobar"

Getting closer :)

Original comment by Shizit.H...@gmail.com on 31 Mar 2010 at 11:05

GoogleCodeExporter commented 9 years ago 
You have arrived at the normal behaviour then - AutoKey doesn't grab the hotkey
combination, so the event still gets through to all other applications. The 
solution
is to add an extra backspace to the start of your phrase/script to get rid of 
the
extra character.

Original comment by cdekter on 31 Mar 2010 at 11:08

GoogleCodeExporter commented 9 years ago 
Again, if I set a hotkey "Win+X" to output "foobar", in Terminal it includes 
the "X".
i.e: pressing "Win+X" will output "xfoobar"

However, if I do this inside of Firefox for example, it works as expected. Any 
way
around this?

Original comment by Shizit.H...@gmail.com on 31 Mar 2010 at 6:58