Tracker Data Entry Improvements #63
Closed
Comments
|
As ESC is reserved, the implementation put forth uses all non-data-entry, yet valid keystrokes to abort data entry. My only gripe is that I selected append-on-entry behaviour for nonzero pattern values instead of clear-on-entry, as I would have preferred. I selected the append behaviour because it followed the existing data entry model and it might be muscle memory for some users. It's an easy fix if we agree that clear-on-entry is the better model. |
burnsauce
added a commit
to burnsauce/teletype
that referenced
this issue
Sep 3, 2017
Buffered input Clear-on-new-entry Apply-on-Enter Abort-on-navigation Incrementers wrap around 16-bit limits Number entry blocks if it would exceed limits
|
clear on entry makes sense. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The data entry on the tracker screen should be buffered, i.e.: users should have to press 'ENTER' to confirm data, and could hit 'ESC' to cancel entry.
It would permit users to enter large values into patterns instantaneously. Currently, intermediary typed values are caught by scripts reading the patterns at high rates -- any rate higher than the data entry speed.
Additionally, this would eliminate the problem of needing to delete the existing data in the field before entering data.
The text was updated successfully, but these errors were encountered: