Currently when we use implicit property nodes and you want to create a "VI Snippet ", the image automatically switches to explicit property nodes. It would be good if this tool will work in this way.
I agree with holding the Implicit property node. But it would be good if we take a snippet of an implicit property node it should also capture the control instead of changing the property node to explicit node along with a reference. This is similar to the condition while copying a Local variable and pasting in another vi the associated control will also be pasted.
-----
The best solution is the one you find it by yourself
I would say that this is actually a bug in the snippet feature. The technical reason for this is that NI used the same code that's used for creating a subVI from a selection, which causes this is as a side effect.
If you want a more immediate solution, try the Code Capture Tool. It produces snippets without these issues and has a number of other useful features, such as including the front panel in the image or backsaving the snippet.
A long time ago I suggested a simple idea which directly addressed this issue (it may not have been obvious). It got about 6 Kudos. If there is a will, there is a way, but there is no will here.
My idea was simple. Use the copy-paste model instead of Create SubVI. It handles event structures, implicit references, actually gets the image of cluster constants correct. However, for some reason, people seemed to like (or think they liked) the current method. Fortunately the Code Capture Tool developers listened to me. Now almost four years later I suggest a simple poll, who are happier with snippets, people using the native tool, or people using the CCT?
The other argument that came up, was that it was "hard" to fix the current behavior. So I tested that out. I wrote relatively simple code to create a snippet with the Create SubVI method instead of Copy/paste and then clean up the mess. After about 6 rounds of "I think it works" followed by "c'mon man!" as I found another glitch, I think it works nicely that way as well.
Right now, the evidence I have suggests the following:
1) Copy/paste is superior to Create SubVI, especially with a few tweaks to automatically include control terminals and remove broken wires if desired
2) It is easy to fix the current method to handle most common uses (implicit nodes, event structures)
