tl;dr There's a summary at the bottom if this is too long for you.
Quick Drop is pretty useful when it comes to dropping things and the fact that it also gets items from the project is great.
What I don't like about QD, however, is the keyboard shortcuts. These allow you to perform custom actions in LV and the concept itself is great, but the implementation QD uses has some issues which other similar tools like the right-click framework and LabVIEW Speak don't have, such as the items in the following list.
So, what can we do about it?
I think a good first step would be to stop thinking of these as "keyboard shortcuts". They should be thought of as custom actions or macros and they should simply appear in the list
along with the regular items, like so:
There are a few things to point out in this image:
OK, so that's step one and it solves the first issue - the actions are discoverable, accessible and not limited in number.
Now step two - some of you may have noticed that the image has another new thing - there's an expand button on the right side.
Clicking that button will open this panel:
This area shows the details of the currently selected action and allows selecting options for it.
Here's what we see in this example:
The panel should remember its last open setting between calls and when it's open, it should work asynchronously, so that it doesn't delay the operation of QD.
For the VIs which appear in the panel, there should be a standard template for loading and saving values, for showing titles and help data and for shutting down. If the VI fails to respond to the shutdown command within N ms, Quick Drop should proceed and not wait for it.
Of course, once we have this panel, the next logical step is to also have it show the help for standard items, similar to this idea:
So, to sum up:
I'm not aware of anything along these lines anywhere. Note that for something like this to work without NI doing it, you would have to recreate the Quick Drop dialog itself and then also create plugins which work with new system (or wrappers around existing plugins which will format the data like each plugin wants it).
Personally, I tend to use the popup menu plugins more often than QD shortcuts, but that's a matter of personal preference.
The only thing I can suggest which you can do immediately is to go into the shortcuts dialog in QD and configure only the shortcuts you actually use, but that still limits you to however many shortcuts can be configure.
I'm not sure about popup menu plugin. However I did try myself changing the shortcuts in QD settings, but the challenge is when each developer has their own shortcuts for different plugin. Most of the time, I myself have to reconfirm and try to remember by looking into the QD settings.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.