08-20-2013 01:19 AM
@Darren wrote:
Specifically, I think it makes the most sense to remove the custom window title from the palette item so its VI name appears in the palette...I always found VIs that dropped with different names than their palette entries to be confusing.
The main problem with that is the the OpenG VIs are namespaced by adding __ogtk to the end of the name, which doesn't look that great and is a problem to change due to legacy support (code has to be able to find the VI).
08-20-2013 08:10 AM
@Darren wrote:
I think until the Quick Drop behavior changes (and we have no plans to change it), the OpenG version of the function should get a different window title so its Quick Drop/palette name is unique. Specifically, I think it makes the most sense to remove the custom window title from the palette item so its VI name appears in the palette...I always found VIs that dropped with different names than their palette entries to be confusing.
This is a good suggestion for our internal reuse library which had a function named "Enqueue Element" I just added some extra text to be able to identify it from the native "Enqueue Element". Something similar could be done with OpenG. Change the Window Title to be "Wait (ms) OpenG", then the namespace can stay the same with the __ogtk.vi suffix but have quick drop find the unique functions.
This unfortunately is a task for OpenG now to "fix", which maybe difficult to do since they may not see this as an issue, but anyone using quick drop and OpenG will find this annoying.
Another annoying side effect is I can't set a shortcut to any of these items either. They may show up in a project because of the dependency loading mentioned earlier, but I can't assign "wat" to the OpenG wait function.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord