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

[BUG] When an unconfigured key is used, the output stops working, even on the paper tape and won't work again until reconnect #1629

Open
Monniasza opened this issue Sep 19, 2023 · 0 comments
Labels

Comments

@Monniasza
Copy link

Monniasza commented Sep 19, 2023

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

Steps to reproduce the behavior:

  1. Configure a key to be empty (not no-op)
  2. Use that key
  3. Write something else on that machine
  4. See that nothing is written

Expected behavior
Nothing happens, and machine works without interruption

Operating system

  • OS: Windows 10
  • Plover Version 4.0.0dev12

Hardware
I'm using Picosteno, but I've forgot to map S1-, so the issue occurred when I wanted to write some numbers

@Monniasza Monniasza added the bug label Sep 19, 2023
@Monniasza Monniasza changed the title [Bug] When an unconfigured key is used, the output stops working, even on the paper tape and won't work again until reconnect [BUG] When an unconfigured key is used, the output stops working, even on the paper tape and won't work again until reconnect Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant