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

Remapping Does Not Work When Target Keyboard is Not Found #3

Closed
iberianpig opened this issue Jan 14, 2024 · 0 comments · Fixed by #5
Closed

Remapping Does Not Work When Target Keyboard is Not Found #3

iberianpig opened this issue Jan 14, 2024 · 0 comments · Fixed by #5
Assignees
Labels
bug Something isn't working

Comments

@iberianpig
Copy link
Owner

iberianpig commented Jan 14, 2024

The issue occurs when the following configuration is set in ~/.config/fusuma/config.yml:

plugin:
  inputs:
    remap_keyboard_input:
      keyboard_name_patterns: xremap

It seems that the issue arises because other keyboard remappers like xremap are not fully initialized, and fusuma starts before them. The expected behavior is that if remapper(virtual keyboard) or external keyboards are connected later, they should also be included in the remapping targets.

@iberianpig iberianpig added the bug Something isn't working label Jan 14, 2024
@iberianpig iberianpig self-assigned this Jan 14, 2024
iberianpig added a commit that referenced this issue Apr 1, 2024
- 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant