09-07-2015 07:24 AM
I am just learning Quick Drop (which is a fantastic productivity tool) and was looking to assemble a Cheat Sheet with icons to help me.
Posting it here in case it is useful to anyone else.
Apologies if my summaries and contractions are less than accurate.
And, yes, I know it's not exactly compact. All on 1 or 2 pages would have been better. Maybe in Version 2 if that ever happens.
09-08-2015 07:15 AM
Pretty neat, not sure if you've seen this or not but here is a more condensed table without icons.
https://decibel.ni.com/content/docs/DOC-20453
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
09-08-2015 05:14 PM
Here is my VI that auto creates the a shortcut documentation based on the ini file and Plugin Ctrl-shortcut
I’ve also attached my practise VI, and the QD-documentation it creats
09-09-2015 10:58 AM
Wow very cool thanks for sharing. I noticed your practice VI is missing the randomize VI but riffle and an OpenG reorder can replace it.
I also noticed the images are missing for some VIs. I believe any merge VIs are missing. Here are a list of some I noticed didn't get images for: Error Constant, Error Ring, Clear Errors, Array Constant, Three Button Dialog.vi, Tick Count (ms) (OpenG), True Constant (but not false constant for some reason), Variant Constant, Wait (ms) (OpenG). I haven't yet looked into why it got no image for these or what could be done.
I'd also suggest an option to sort based on the object name, or shortcut. The previously linked spreadsheet has both and I found it useful.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
09-09-2015 12:58 PM
Okay it looks like part of the problem is the path constant you had pointing to your user.lib. I replaced this with the OpenG User Library path constant, and this improves it a bit. I also had to wrap the pattern string in * before and after the command to help find the subVI.
This still has issues because I have some commands that aren't the full name of the VI. The command for QD can come from the VI title so the OpenG Wait has a VI title "Wait (ms) (OpenG)" but the VI name is
"Wait (ms)__ogtk.vi". So searching for the VI named "Wait (ms) (OpenG)" will not find the right one.
Another issue is commands that aren't in the user.lib, but also aren't part of the styles. I tried searching all of the installed LabVIEW directory but this took forever and still didn't find them all. I'm thinking to do this right you may need to use the Place Object on Cursor, then programatically drop the item. The benefit of this is you can then drop the item using the same QD name and not worry about the VI name or where it is. This will also produce the image of the dropped code for merge VIs and not the VI icon.
A cleaner version would obviously be to drop an object using the QD name, but I do not know of a function that does that. The closes is the function that puts it on your cursor which might work if we are quick and the user doesn't move the mouse.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord