-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Visual glitch when using backspace to clear text on multiple rows #59
Comments
Hi @Mithil467, can I pick up this issue. |
Hey @sks147 👋 |
Sure. |
Since it has been a long time and no update seems to happen, Can I work on this issue? |
Hi @jai-dewani, you can pick up this issue. @Mithil467 really sorry for no updates on this. I got really busy. |
Actually, I was thinking about this. If the user spams keys, the app will crash when it is no longer possible to fit all the characters on a given screen window. But, again this will cause issues if user types till the maximum length possible, but then resize the window and shrink its width. So restricting the length to a fixed constant like 20 sounds right (instead of the entire screen width). |
@sks147 That's totally fine :) |
Okay, restricting Do you think we should inform the user in some way about him reaching the limit of the wrong letters he has typed? Maybe a sound or a textual message at the bottom left/right saying |
Wow, that seems like an even better indicator, I'll get going then. I'll create a separate variable for the limit on |
Yes. That'd be great :) |
Steps to reproduce:
Start mitype, preferably with a relatively lesser width terminal window.
Spam any wrong keys so that the text overflows to next line as shown below.
Try to clear those keys by pressing backspace.
Expected behaviour
Backspace should clear all the keys consistently.
Actual behaviour
The logic works as expected and does indeed clear text but doesn't update the screen visually for the lines below, but works fine for top line.
Proposed fix
Maybe we need to clear the entire screen if that is feasible.
The text was updated successfully, but these errors were encountered: