You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Jumble currently allows all characters to be typed using keyboard and on-screen keyboard. This is not ideal, as most characters will never be part of the solution.
Describe the solution you'd like
The input for not to allow non-solution characters for entry. A beep/jiggle or something to signify invalid input (This is currently done only at the end of submission).
The on-screen keyboard to visually show that the character cannot be typed (button disabled).
Describe alternatives you've considered
N/A
Additional context
State of things
Example solution
The text was updated successfully, but these errors were encountered:
Neat project! I'd be interested in taking on this issue. I'm thinking of implementing a disabledKeys property for the WordInput component which would allow Jumble to specifically disable non-playable characters. How does that sound?
Hej @paulkim26. Thank you for the interest in the project.
Sounds good. Although WordInput has a targetValue string being passed to it. Disabled keys can possibly be inferred from it. I'll leave you to take a call.
Is your feature request related to a problem? Please describe.
Jumble currently allows all characters to be typed using keyboard and on-screen keyboard. This is not ideal, as most characters will never be part of the solution.
Describe the solution you'd like
Describe alternatives you've considered
N/A
Additional context
The text was updated successfully, but these errors were encountered: