Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Some extra keys are being treated as steno keys #1289

Open
JorWat25 opened this issue Apr 22, 2021 · 2 comments · May be fixed by #1357
Open

Some extra keys are being treated as steno keys #1289

JorWat25 opened this issue Apr 22, 2021 · 2 comments · May be fixed by #1357
Labels
bug confirmed windows

Comments

@JorWat25
Copy link

Describe the bug

When Plover is active on my laptop, the mute and volume down keys become W and A keys respectively. According one website, they are keys <181> and <182>.

To Reproduce

Steps to reproduce the behavior:

  1. Activate Plover
  2. Press the mute or volume down keys
  3. See W or A

Expected behavior

Either nothing should happen, or the keys should do their usual function.

Operating system

  • OS: Windows 10
  • Plover Version 4.0.0.dev9

Hardware

The laptop is an Lenovo Ideapad.

I should note it is only the laptop keys that do this. An external keyboard, also with volume keys apparently with the same code numbers, works normally when Plover is activated.
@JorWat25 JorWat25 added the bug label Apr 22, 2021
@user202729
Copy link
Member

user202729 commented Jun 11, 2021 •
edited
Loading

Plover reads scan code rather than virtual key code (vkCode).

I don't know what was the purpose (does it make a difference with Dvorak keyboards? Or something else?), given that Plover also use vkCode to determine if a key is a modifier key (PASSTHROUGH_KEYS).

A possible fix is: (moved to pull request)

This fix has the side effect that the / and Return keys on the number pad will not be mappable with this change. (not tested)

Or is it better to use vkCode for both?

@user202729 user202729 linked a pull request Jun 18, 2021 that will close this issue
Open
2 tasks
@khonkhortisan
Copy link

I have the exact same problem on a 💻Dell Latitude E6410: volume down is a, volume up does nothing, mute is with, volume down+mute is was. Those three buttons' normal behaviour is blocked while plover is enabled; the volume doesn't change.
These are the buttons autohotkey sees pressed when plover is disabled and I press down up mute.

VK  SC	Type	Up/Dn	Elapsed	Key		Window
-------------------------------------------------------------------------------------------------------------
AE  12E	 	d	1.81	Volume_Down    	
AE  12E	 	u	0.08	Volume_Down    	
AF  130	 	d	0.48	Volume_Up      	
AF  130	 	u	0.14	Volume_Up      	
AD  120	 	d	0.50	Volume_Mute    	
AD  120	 	u	0.17	Volume_Mute

These are the buttons autohotkey sees pressed when plover is enabled and I press down up mute and it types awith

VK  SC	Type	Up/Dn	Elapsed	Key		Window
-------------------------------------------------------------------------------------------------------------
AE  12E	 	d	2.03	Volume_Down    	
AE  12E	 	u	0.05	Volume_Down    	
20  039	#	d	0.03	Space          	
20  039	#	u	0.00	Space          	
41  01E	#	d	0.00	a              	
41  01E	#	u	0.00	a              	
AF  130	 	d	0.34	Volume_Up      	
AF  130	 	u	0.11	Volume_Up      	
AD  120	 	d	0.38	Volume_Mute    	
AD  120	 	u	0.16	Volume_Mute    	
57  011	a	d	0.02	w              	
57  011	a	u	0.00	w              	
49  017	a	d	0.01	i              	
49  017	a	u	0.00	i              	
54  014	h	d	0.00	t              	
54  014	a	u	0.00	t              	
48  023	a	d	0.00	h              	
48  023	a	u	0.00	h

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug confirmed windows
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Do not consider extended scan codes in Windows user202729/plover
3 participants
@khonkhortisan @user202729 @JorWat25