Activity log for bug #1648336

Date Who What changed Old value New value Message
2016-12-08 08:00:09 RaiMan bug added bug
2016-12-08 08:00:24 RaiMan sikuli: status New In Progress
2016-12-08 08:00:29 RaiMan sikuli: importance Undecided High
2016-12-08 08:00:33 RaiMan sikuli: assignee RaiMan (raimund-hocke)
2016-12-08 08:00:36 RaiMan sikuli: milestone 1.1.1
2016-12-08 11:27:51 RaiMan description I've made some tests on last 1.1.1 (Win7-64) and revealed the following thing in using Env.addHotkey function: #1. There is a little mess with key modifier using in addHotkey, for example: Env.addHotkey(Key.F11, KeyModifier.CTRL, handler) # works as expected Env.addHotkey(Key.F11, KEY_CTRL, handler) # works as expected too Env.addHotkey(Key.F11, Key.CTRL, handler) # fails # another example: Env.addHotkey(Key.F11, KeyModifier.WIN, handler) # doesn't fail but doesn't work as expected Env.addHotkey(Key.F11, KEY_WIN, handler) # works as expected Env.addHotkey(Key.F11, Key.WIN, handler) # fails This needs to be standardized (an issue with obsolete constants). Also in removeHotkey function, I suppose. #2. Env.addHotkey(Key.F12, 0, handler) # see below This is passed but generally doen't work on Windows. The solution is to change system debugger hotkey in the registry: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\UserDebuggerHotKey from 0 to any suitable value (0x2F for example), then reboot; this will turn off the debugger hotkey F12 and release this key to use as Sikuli hotkey. Also SHIFT+F12 hotkey can't be set without registry tweaking. But CTRL+F12 can be successfully set, I did it on my Windows 7 machine. ************ comment on fix --- fixed: KeyModifier.WIN now is the same as KEY_WIN --- not fixed: the usage of Key.KEYNAME is not allowed as modifier key (2nd parameter) with addHotKey() - use only the constants from class KeyModifier (the constants KEY_XXX are pre-imported in Python scripting and hence can be used without class name) --- not fixed: Key.F12 alone or with SHIFT seems to be blocked in the standard (I will add a note to the docs) ------------------------------------------------------------------ I've made some tests on last 1.1.1 (Win7-64) and revealed the following thing in using Env.addHotkey function: #1. There is a little mess with key modifier using in addHotkey, for example:          Env.addHotkey(Key.F11, KeyModifier.CTRL, handler) # works as expected          Env.addHotkey(Key.F11, KEY_CTRL, handler) # works as expected too          Env.addHotkey(Key.F11, Key.CTRL, handler) # fails          # another example:          Env.addHotkey(Key.F11, KeyModifier.WIN, handler) # doesn't fail but doesn't work as expected          Env.addHotkey(Key.F11, KEY_WIN, handler) # works as expected          Env.addHotkey(Key.F11, Key.WIN, handler) # fails This needs to be standardized (an issue with obsolete constants). Also in removeHotkey function, I suppose. #2.          Env.addHotkey(Key.F12, 0, handler) # see below This is passed but generally doen't work on Windows. The solution is to change system debugger hotkey in the registry: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\UserDebuggerHotKey from 0 to any suitable value (0x2F for example), then reboot; this will turn off the debugger hotkey F12 and release this key to use as Sikuli hotkey. Also SHIFT+F12 hotkey can't be set without registry tweaking. But CTRL+F12 can be successfully set, I did it on my Windows 7 machine.
2016-12-08 11:27:56 RaiMan sikuli: status In Progress Fix Committed
2016-12-08 11:27:59 RaiMan sikuli: importance High Critical
2016-12-08 11:28:29 RaiMan summary [1.1.1] Windows: Hotkey modifiers don't work correctly & F12 hotkey problem [1.1.1] Windows: Hotkey modifiers don't work correctly & F12 hotkey problem - fixed 1.1.1 nightly 2016-12-09