05-17-2012 01:02 PM
I'm just curious about the QD filtering on the ctrl-key shortcut menu. Is it looking at the connector pane? I realized that just because a VI is in the plugins directory, doesn't mean it will show up in the QD ctrl-key shortcuts (i.e. subVIs you may use in your top level QD VI). This is obviously fine, because I don't want these VIs to be selected as QD plugins, but I was just looking for clarification.
05-17-2012 10:02 PM
Until the definitive answer arrives I will say that it appears that placing magic text in the VI description gets it into the list, and backwards compatibility is maintained by assuming all VIs with single letter names are shortcuts. Type checking (ie. the ConPane) is apparently not checked until it is time to run it.
05-21-2012 03:28 PM
WARNING: This is probably more than anybody (besides me) ever wanted to know about how Quick Drop determines the validity of keyboard shortcut plugin VIs.
Depending on the LabVIEW version, different approaches are taken to determine which Ctrl-Key shortcuts are available. In each scenario below, I use the following path abbreviations:
[resourceplugins] - <LabVIEW>\resource\dialog\QuickDrop\plugins
[lvdataplugins] - <LabVIEW Data>\Quick Drop Plugins
I'd like to unpassword-protect some of the VIs that do this parsing so y'all can take a look for yourselves if you so desire. However, there are a couple of private VI Server calls that I'd need to get publicized before I can do that. I'll see what I can do for LabVIEW 2013.
05-21-2012 03:37 PM
Thanks Darren! A side note with regard to templates: could you possible set the template as a .vit? On more than one occasion I have saved without being forced to rename, and my VI becomes the template
05-21-2012 03:47 PM
A side note with regard to templates: could you possible set the template as a .vit?
That's a reasonable suggestion. I've posted it here for discussion. Please add your thoughts there...I'm particularly interested to know if the file rename will have any adverse effects that I can't think of.
03-13-2021 12:10 AM
Bumping this ancient thread.
Did we ever get access to the VIs that filter the QD list?
One thing I'd love to do is modify the filtering to prioritize my project's PPL Actor Framework methods over the vi.lib Actor Framework messages. If there are any hooks I can use to modify this sort of thing, that would be great.
03-14-2021 05:36 PM
This thread is referring to the plugin VIs that implement Quick Drop Keyboard Shortcuts (pressing Ctrl-[key] to launch a tool from Quick Drop). It sounds like you're asking about the list of objects in Quick Drop itself, and wanting to customize the order in which items appear, as you are using a built PPL of the Actor Framework instead of the original Actor Framework itself. For example in the situation you describe, if you type 'launch root actor' in Quick Drop, you would see this:
You would rather see the PPL version of the VI appear first in the list. Am I understanding the issue correctly? If so, can I offer a very low-tech solution? Just type 'libp' before typing the name of the method you want:
For project items, Quick Drop uses simple string matching, so if the string appears anywhere in the item name, it will be a match. So in this case, since we know all of the AF PPL methods will be in "Actor Framework.lvlibp", we can type a string that is unique to that library (in this case, 'libp' is unique enough) to filter the Quick Drop list appropriately.
This is the approach I use when doing a search in Quick Drop for project items... when I know the thing I want is in a particular class or library, I'll type a few characters of the class/library name and then start typing the name of the VI and it usually works well.
I hope this low-tech solution is sufficient, because I just dug into the Quick Drop code and it looks like palette matches are always placed above project matches in the list, and there's no way to customize that (without editing the password-protected main Quick Drop VI).