06-10-2015 03:50 AM
I have a logitech G600 mouse.
I've programmed 3 of the button to play a macro...
When hovering over a terminal....
1. Right click (brings up the context menu)
2. Type, CRE (goes to create)
3. Press the right arrow (Opend the create menu)
4. Type, DownDownEnter
This little macro creates and indicator for a terminal in about 0.3seconds I've also got a button for control and constant (they just change hown many times the down arrow is pressed).
06-10-2015 08:15 AM
There are many great ideas here...
Thanks to everyone for sharing you ideas and methods!
This discussion reminded me of a time (yep, I'm old) when software (boxes) include plastic overlays to drop around the function keys. These overlays provided labels for the custom function when the function key was pressed while using that software. I'm thinking that application specific function keys might be a good way to get to my favorite QDs with single key press, but then I'll have to make a custom overlay so I can remember My LV F-Key assignments.
First, I'll need to learn how to assign macros to function keys:
https://support.microsoft.com/en-us/kb/237179
Cheers
06-10-2015 08:20 AM
I looked into AutoIt and it might be a good solution. It is closer to a full programming language where we could do things like only perform a macro if a LabVIEW window is selected.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
06-10-2015 08:30 AM
Hello,
I'm using a VI witch is running in Background and observes the actual VI with focus.
It also observes the keyboard. If I use Space and some other key it makes VI Scripting like creating a variable, switch the direction of a control <> indicator, show/hide Scrollbars, ...
Take a look at the screenshots ...
So you can start a script like with QuickDrop, but quicker 😉
You can start such an action also if you hit F1 or any other Key without Space. But normally if you hit k,w,o, ... you want that LabVIEW writes these letters!?
required settings
06-10-2015 12:26 PM
I'm using the razer product for a couple of year now, I'm really satisfied with my setup:
http://www.razerzone.com/ca-en/store/razer-deathstalker
http://www.razerzone.com/ca-en/store/razer-naga
http://www.razerzone.com/ca-en/store/razer-tartarus-classic
The three product can work together to change the mapping of each device and change the set of macros the are assigned to each key. So you can assign hundred of macros. After that you need to remember all the mapping you have configured... That's the hardest part.
Dany
06-11-2015 02:22 AM
sletrab wrote:
If I use Space and some other key it makes VI Scripting
Ah, that's a fairly decent workaround to the issue I had - assuming that the user will not hold space+another key at the same time (although how does this work with Ctrl+Space?). It still means you're limited to N actions, but it's decent.
Years ago I did something similar where I had a few specific actions I wanted to perform in many places in some VIs which required user intervention. I had a similar VI which simply monitored for a single key press and did the relevant action. In my case it was fine, because the operation was done at a very specific point in time, but I seem to remember that one of my coworkers managed to cause it throw an error dialog because he went and started typing something instead of doing that operation.
06-11-2015 02:47 AM
Do I get this correctly? When having a VI in focus and writing a simple comment text on the BD - as soon as I type space, your functionality will come into action?
(Actually I assume that it won't, but just to be clear...)
06-11-2015 03:07 AM
comrade wrote:
Do I get this correctly? When having a VI in focus and writing a simple comment text on the BD - as soon as I type space, your functionality will come into action?
(Actually I assume that it won't, but just to be clear...)
The code only acts if there are two keys pressed at the same time and one of them is space.
06-11-2015 04:11 AM
Hello comrade,
Yes there is a hidden Event "VI Activation". This Event fires, when the VI with Focus change. And you can differ if the BD or FP has the focus.
You can also obsere the keyboard and start a script if special Key(s) are pressed.
If I have selected a local variable or indicator or control and press Space+d it toggles the direction.
If I have selected an indicator or control and press Space+p a property node will be created.
If I have selected an indicator or control and press Space+v a local variable will be created.
...
If someone is really interesting, I could give out parts of the code.
comrade wrote:
Do I get this correctly? When having a VI in focus and writing a simple comment text on the BD - as soon as I type space, your functionality will come into action?
(Actually I assume that it won't, but just to be clear...)
No you do not write a comment, you select something which is no valid aim for keyboard input (like a control or a SubVI), then you you press the keys
06-11-2015 04:27 AM
Just to be clear, the basis of sletrab's code is Norm's scripting springboard. Search for that and you would have the bulk of the code.