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

NumPad now restores the former num lock state on deactivation. #3

Merged
merged 1 commit into from Mar 9, 2018

Conversation

MartyGentillon
Copy link
Contributor

this resolves #1

@algernon algernon self-assigned this Mar 1, 2018
@algernon algernon merged commit 78710d0 into keyboardio:master Mar 9, 2018
MartyGentillon added a commit to MartyGentillon/Kaleidoscope-NumPad that referenced this pull request 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 keyboardio#2
see keyboardio#3
see keyboardio#1
see keyboardio#6
MartyGentillon added a commit to MartyGentillon/Kaleidoscope-NumPad that referenced this pull request 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 keyboardio#2
breaks keyboardio#3
see keyboardio#1
fixes keyboardio#6
MartyGentillon added a commit to MartyGentillon/Kaleidoscope-NumPad that referenced this pull request 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 keyboardio#2
broken keyboardio#3
see keyboardio#1
fixes keyboardio#6
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.

NumLock state always remains on
2 participants