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

Tracker Data Entry Improvements #63

Closed
burnsauce opened this issue Jan 17, 2017 · 2 comments
Closed

Tracker Data Entry Improvements #63

burnsauce opened this issue Jan 17, 2017 · 2 comments

Comments

@burnsauce
Copy link
Contributor

@burnsauce burnsauce commented Jan 17, 2017

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.

@burnsauce
Copy link
Contributor Author

@burnsauce burnsauce commented Sep 3, 2017

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
@tehn
Copy link
Member

@tehn tehn commented Sep 6, 2017

clear on entry makes sense.

@tehn tehn closed this in ad358cd Oct 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants