Front Panel Snippets

[Darin.K]

This recent idea pushed me to finally suggest something I have been mulling for a while.  One of my primary uses for snippets is for custom controls, the code is simply the BD terminal.  I customize the snippet to use the FP image so that the thumbnail view of Windoze explorer becomes an effective orginizational tool.  Two steps keep this from being a totally fluid process (1) I have to use custom code in a QD/RCF shortcut to create the snippet (2) I have to drag the snippet to the BD, or extract the code using another QD/RCF shortcut.  To remedy this I suggest that we add the ability to create snippets from front panel objects.  Either limit the selection to a single object and cram the .ctl file into the PNG metadata, or you can simply do the same thing as for BD snippets and put the .vi file in there with only the control terminal(s).  The image should be of the control itself, and we should be able to drag and drop to the FP.  

Added features:  I think that we should be able to drop all snippets on the FP, and I still wish that Select a VI... would allow us to choose snippets, except now Select a Control... should probably as well.

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Select-a-VI-should-permit-Snippets/idi-p/1446954

[SteveChandler]

I wish snippets sucked in all the subVIs as well as the custom controls.

[AristosQueue (NI)]

Why would you use front panel snippets instead of just using .ctl files? .Ctl files meet all your requirements: made from the front panel, droppable on the front panel, preserve the custom control in a file.

[Darin.K]

Because Windows Explorer in Thumbnail mode is a very efficient way to arrange and select the desired control.  I can organize and search easily, grab several controls at once, include multiple controls in a single snippet.  Create in a single click instead of going through the control editor, share easily on the forums or community pages.  Dragging from explorer does not disrupt my File Dialog start path.  Should I continue?

[AristosQueue (NI)]

The .jpgs are opaque to LV's search abilities, you can't find-and-replace text, they don't update if you have nested controls, they don't reflect system color changes... Should I continue? 🙂 Seriously, though, both files have uses. I guess I'd be more inclined to see .ctl files enriched with all the aspects you describe rather than extend further the .jpgs. For example, in LV 2011, you can create them in one click without opening the control editor. Right click on a control and choose the new option "Make Typedef".

[Darin.K]

By jpg you mean png. Which search are you referring to? It would have to involve files on disk because the png is never in memory, only the embedded control. In addition, I have snippets with nested type defs and it works just fine in terms of what is dropped. It seems to me that the simple addition to snippet capability is simpler than an overhaul to ctl format. Both Microsoft and Apple have put a lot of effort in organizing and previewing image files, and it would seem possible to do a better job leveraging it. To paraphrase, I would *hate* it if NI spent developer time reinventing windows explorer.

[Manzolli]

I'm more prone to not kudos this idea. If I want a group, I can create a VI with a template of the controls. When I want to use, I open the VI, copy and past it wherever I want.