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

A17: oddness with keyboard editing of grbl settings #29

Closed
phil-barrett opened this issue Apr 24, 2020 · 2 comments
Closed

A17: oddness with keyboard editing of grbl settings #29

phil-barrett opened this issue Apr 24, 2020 · 2 comments

Comments

@phil-barrett
Copy link
Collaborator

This appears to be a bug in the keyboard manipulation of 4 digit numbers in text boxes. My example is for Id 25 (Homing search seek rate) but it appears to apply to all numeric text boxes..

  • Open the Settings: Grbl tab.
  • Select id 25 by clicking on the row in the table on the left (Homing search seek rate). Enter 5000 in the text box. Press save (or enter).
  • note that the entry in the Value column changes to 5000
  • press reload. Note the Value column entry has added .000 to the value

(the above is just to set the situation up to demonstrate the bug)

  • select Id 25 as above
  • place the cursor after the 50 in the 5000.000 shown in the text box on the right.
  • delete a 0 so that the box shows 500.000 and press enter.
  • note that the Id 25 Value column entry changes to 5000 (not .000 following).
  • press save and then reload. the Value column entry has changed to 5000.000 and exit box on the right still shows 500.000
  • expect results are 500.000 in the Value column entry for Id 25

This appears to be the case for all values edited, not just Id 25. Note that if you change the leading digit or completely rewrite the value, it works correctly.

@terjeio
Copy link
Owner

terjeio commented May 1, 2020

Looks like a framework bug to me, the OnPreviewTextInput event does not fire on all changes. I have added a handler for OnPreviewKeyUp to trap and process delete and backspace keys as a workaround.

@phil-barrett
Copy link
Collaborator Author

phil-barrett commented May 1, 2020

Makes sense to me. They probably had a college intern working on that part... Thanks for fixing it.

terjeio added a commit that referenced this issue May 9, 2020
Fixes/updates for #29, #30, #31 and #32. A number of other changes and improvements.
@terjeio terjeio closed this as completed May 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants