Skip to content
This repository has been archived by the owner on Jul 13, 2021. It is now read-only.

Numpad now properly restores the former numlock state on deactivation. #7

Merged
merged 1 commit into from
Aug 11, 2018

Conversation

MartyGentillon
Copy link
Contributor

@MartyGentillon MartyGentillon commented Mar 15, 2018

Test procedure:

  1. Make sure numlock is off on host machine.
  2. Activate num layer. Confirm, numlock is now on.
  3. Deactivate num layer. Confirm, numlock is now off.
  4. Using another keyboard, activate numlock on host machine.
  5. Activate num layer. Confirm, numlock is still on.
  6. Deactivate num layer. Confirm, numlock is still on.

Prior to this commit, step 6 resulted in numlock being off.

see #2
was broken #3
see #1
fixes #6

Test procedure:
  1. Make sure numlock is off on host machine.
  2. Activate num layer. Confirm, numlock is now on.
  3. Deactivate num layer. Confirm, numlock is now off.
  4. Using another keyboard, activate numlock on host machine.
  5. Activate num layer. Confirm, numlock is still on.
  6. Deactivate num layer. Confirm, numlock is still on.

Prior to this commit, step 6 resulted in numlock being off.

see keyboardio#2
broken keyboardio#3
see keyboardio#1
fixes keyboardio#6
@obra obra merged commit 386787f into keyboardio:master Aug 11, 2018
@obra
Copy link
Member

obra commented Aug 11, 2018

Thank you! Applied. I'm sorry I let this sit so long.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Regression: Deactivating the Number layer now disables numlock even when it was already on on host machine.
2 participants