- TNGv2 Feature request - using inputs to respond to dialogs
-
Member
TNGv2 Feature request - using inputs to respond to dialogs
I have 3 buttons wired up to inputs 2,3,4 and configured for start, pause, stop and the keyboard and mouse are in a drawer that I keep closed while running code so that it doesn't fill with swarf. It would be really nice if those buttons could be used to respond to dialogs (ie. the Start button == OK, the Stop Button == Cancel). The main use for me would be to respond to tool change dialogs without having to open the keyboard drawer to hit enter (or escape if needed).
I finally installed v2 on the computer that controls my mill today and really like how it is so much more flexible that the last version (which was pretty good as well). The new one is taking a big step up. Loving your work
Cheers
Simon
Similar Threads:
-
-
Member
Re: TNGv2 Feature request - using inputs to respond to dialogs
Makes perfect sense. I'll see what I can do.
-
Member
Re: TNGv2 Feature request - using inputs to respond to dialogs
This is just implemented for g-code dialogs :-)
-
-
-
Member
Re: TNGv2 Feature request - using inputs to respond to dialogs
I'm glad it works fine and it seems like a good feature.
I was thinking that perhaps this should be specially enabled in settings and not turned on by default. Do you think this is reasonable?
-
Member
Re: TNGv2 Feature request - using inputs to respond to dialogs
That might be a good idea. You could possibly add a couple of extra shortcuts for Dialog->OK and Dialog->Cancel then you could assign anything to them (could be different buttons for example). You would have to make those shortcuts able to reuse inputs that are assigned to something else though.
While I was just looking at the shortcuts I noticed under File, Open File and Open Code. Those don't exist in the menu and when I assigned a keycode to those they don't appear to do anything. Are they meant to be there? If so what are they meant to do?
-
Member
Re: TNGv2 Feature request - using inputs to respond to dialogs
Those two commands require argument (filename or g-code). They are useful in script/expression/api.
- TNGv2 Feature request - using inputs to respond to dialogs
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules