07-02-2010 05:04 PM
In this thread, JG requests the ability to cache a quick drop plugin VI. In LabVIEW 2009 (and 2010), Quick Drop, along with any launched plugin, leaves memory after each use. So native caching of Quick Drop and/or plugin VIs is not currently possible.
That being said, I came up with an alternative approach that effectively "caches" a plugin VI. In this approach, Quick Drop and its plugin still leave memory each time, but the first time the plugin runs, it launches a spawned VI that stays in memory. Whenever the plugin runs, it sends a message (via queue) to the spawned VI to have it perform some action. If that message is 'quit', the spawned VI leaves memory. There is no auto-cleanup of the spawned VI going on, so it will stay in memory unless you send it a 'quit' message or you exit LabVIEW. It's not the prettiest solution, but it's does allow for "caching" of a VI that one or more plugins can call into whenever Quick Drop runs.
Follow these steps to try out the cached plugin with LabVIEW 2009 or later:
07-06-2010 02:54 PM
Any way to do something similar for the main QD window? (Already selected "Load palettes during launch" but still catch myself typing shortcuts before the QD window is finished loading.)
07-06-2010 11:34 PM
Not in 2010, but I'm investigating some options in 2011.
-D