-
-
Notifications
You must be signed in to change notification settings - Fork 763
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
Start button high risk of miss clicking it #2440
Comments
Thanks for the feedback. Similar requests has been made before with the suggestion to add a popup asking if the user really wants to run the program. I would probably go crazy having to confirm every time I started a job, so I would probably want a checkbox in the confirmation popup to never ask again. I am also interested to learn why you feel that the play button should open a new file. For instance is there another software you have been using that behaves like this? |
Sounds like a perfect solution!
I do not expect that the play button should open a new file. It is just misclicking. I just click the wrong button. I think, it is because somehow mentally the play button looks more dominant (like it does more thing) than the file open button, and this might divert my attention to it. |
Description
Hi,
I have the problem, that sometimes I missclick the start button. It is happening not so often, but still when it happens it is annoying. Usually I want to load an other file, and somehow I click the start button. Then the machine starts to mill.
For this I could imagine a new feature, where next to the start button a check box is there, which have to be marke, in order that the start button becomes enabled. Once the milling is finisched (G code M2 to detect maybe?) the start button should become again unavailable. But during the milling the start button should stay available. This way the missclicking of the button could be reduced.
Not sure if others have also the problem. So I think it is fine if you just reject this issue if you think it is not worth to implement such a feature.
Thank You!
The text was updated successfully, but these errors were encountered: