sikuli-driver team mailing list archive

[RaiMan <sikulix@xxxxxxxxxxx>]

Public bug reported:

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.

** Affects: sikuli
     Importance: High
     Assignee: RaiMan (raimund-hocke)
         Status: In Progress

** Changed in: sikuli
       Status: New => In Progress

** Changed in: sikuli
   Importance: Undecided => High

** Changed in: sikuli
     Assignee: (unassigned) => RaiMan (raimund-hocke)

** Changed in: sikuli
    Milestone: None => 1.1.1

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1648336

Title:
  [1.1.1] Windows: Hotkey modifiers don't work correctly & F12 hotkey
  problem

Status in Sikuli:
  In Progress

Bug 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1648336/+subscriptions