search

numberscope / frontscope

Numberscope's front end and user interface: responsible for specifying sequences and defining and displaying visualizers
MIT License
7 stars 15 forks source link

Don't modify the user's keystrokes #413

Open gwhitney opened 3 months ago

gwhitney commented 3 months ago

Some parameters currently "autocorrect" when an input value is too high. However, this can feel confusing because it seems as though the interface is actually losing keystrokes. At a meeting not long ago, we decided to avoid altering user input and instead implement a warning facility to tell the user that we are proceeding as if the input were different.

In addition/similar vein, we discussed using browser built-in entry fields for numbers/integers as appropriate rather than rolling our own, as it were.

gwhitney commented 3 months ago

The warning facility is heading for branch ui2 in #406. Once that's merged, what will remain here is switching to warning rather than altering input in other visualizers (and sequences, if there are any such instances), and switching to a dedicated number-entering html element for the appropriate fields.

gwhitney commented 2 months ago

This should be taken care of in the individual visualizer "overhaul" PRs, which will have an alpha milestone, so applying that same milestone to this issue.