Num lock turned on: KEY_SHIFT and function keys will not work
Bug #610804 reported by
sotn3m
This bug report is a duplicate of:
Bug #894312: [check] Windows: Selecting text using SHIFT + HOME does not work --- workaround.
Edit
Remove
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
In Progress
|
Medium
|
RaiMan |
Bug Description
Machine: Windows Xp/Windows 7
Sikuli 0.10.1
When "Num lock" is turned on, KEY_SHIFT is not working with function keys.
This:
type(Key.END, KEY_SHIFT)
will not work.
keyDown/keyUp neither.
summary: |
- When Num lock is turned on, KEY_SHIFT and function keys will not work + 0.10.1 Num lock turned on: KEY_SHIFT and function keys will not work |
summary: |
- 0.10.1 Num lock turned on: KEY_SHIFT and function keys will not work + Num lock turned on: KEY_SHIFT and function keys will not work |
Changed in sikuli: | |
status: | Won't Fix → Confirmed |
status: | Confirmed → In Progress |
assignee: | nobody → RaiMan (raimund-hocke) |
milestone: | none → x1.0 |
tags: | added: fkt-type |
Changed in sikuli: | |
importance: | Undecided → Medium |
Changed in sikuli: | |
milestone: | x1.0 → x1.1 |
To post a comment you must log in.
I believe this has to do with SIkuli actually using the numerical part of the keyboard when sending these commands.
Key.RIGHT is actually(using a keyboard pressed with fingers) Shift+NUM6.
When doing(in Sikuli):
type(Key.END, KEY_SHIFT)
...this happens:
SHIFT+NUM1 which is actually only End instead of Shift+End.
Something like this is the issue since I have solved a problem with using IBM iSeries acces and replacing the numerical arrow keys inside the iSeries keyboard map with [mark down] [mark up] etc.