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.

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

Wait for device removal and reload keyboard #5

Merged
merged 2 commits into from
Apr 15, 2024
Merged

Conversation

iberianpig
Copy link
Owner

@iberianpig iberianpig commented Apr 15, 2024

  • Watch for device removal and reload the keyboard.
    • fix error that keyboard is not loaded at startup when using other virtual keyboards.
  • Send current layer via the Fusuma Input plugin to identify the remapped keys.
    • Use MessagePack format to send the data.

Closes: #3

- Wait for 3 seconds and try again if no keyboard is found.
- When a device is removed, reload keyboards and grab them again.

Closes: #3
@iberianpig iberianpig changed the base branch from main to feat/remap-pointer April 15, 2024 09:17
Base automatically changed from feat/remap-pointer to main April 15, 2024 09:20
@iberianpig iberianpig changed the title Wait for device removal and reload the keyboard Wait for device removal and reload keyboard Apr 15, 2024
@iberianpig iberianpig merged commit 6946056 into main Apr 15, 2024
8 checks passed
@iberianpig iberianpig deleted the fix/watch-keyboard branch April 15, 2024 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remapping Does Not Work When Target Keyboard is Not Found
1 participant