Using alphanumeric keys directly

[comrade]

Thanks for this clarification - I thought the keys are pressed in direct sucession.

[#2]

Hello tst,

I knew that I found the idea somewhere, but I did not remember where.

https://decibel.ni.com/content/groups/labview-apis/blog/2009/06/15/automating-labview-development-wi...

It was from NJKirchner. Thank you!

It is without starting scripts via keyboard strikes. I think you must implement the scripts by yourself, but it shows the starting point.

[whitenoiz]

     Thanks for all of your input so far! All the effort you put in to come up with individual workarounds shows me even clearer that there's a need since the emperor simply has no clothes and I'm safe to use keys as they come.

  I'd love to take that unused regular alphanumeric key estate to make those hard to memorize QD shortcuts and functions more accessible in a straightforward way that is intuitive enough even to facilitate learning LabVIEW without requiring additional input devices. It's LabVIEW's arcane user interface that keeps many people from performing their best (good for us! right? Heck, you can even watch pros fumble around menus across virtually all LV video tutorials.

Currently I'm collaborating with a Windows AHK scripting pro and he's already made most things possible that I hadn't even dreamed of before. Cleanup a wire? Hover over it and press w. Set/unset a breakpoint? Just hover and press b. Comment out some code with the Diagram Disable Structure? Just press d and select your region. While for the former, I used the related action's first letters, it still would be great to find a vocabulary along with a set of QD shortcuts that a vast majority of seasoned developers would agree on as basic and essential.

What do you think would be a good way to share my pre alpha version for you to try? Most probably I could prepare an .exe, however understand that it might not appeal to everyone for security reasons...

[#4]

Hello whitenoiz

I would be interested in your work. Please share it.

[tst]

If it helps, AQ has a couple of cryptic comments here that hint there might be some improvement in this area. August and LV 2015 is a couple of months away, so I guess you'll find out then.

As for distributing AHK stuff, I don't have any experience with it beyond playing with it a tiny bit years ago, but I assume you can simply export the scripts and post that for people who don't trust external EXEs.

As for a vocabulary, I have an idea here for making plugin access more accessible in QD and maybe you can do something similar? I'm guessing AHK isn't built for that, though. I did implement it in the QD-like version that I use, but unfortunately I can't share that.