snippet + "allow debugging"

[ouadji]

hello,

LV2013

When i use "create snippet from selection", why this snippet does not keep the original value of  "vi properties / allow debugging" ?

If the original VI has "allow debbuging" OFF ... the snippet changes the value of "allow debbugging" to ON.  Why ?

Is this a small bug ?

(Sorry for my bad english, i do my best.)

[RavensFan · Accepted solution]

What is the property of the VI you are dropping the snippet into BEFORE you drop the snippet into it?

A snippet is a portion of code, it isn't a VI in itself, so I wouldn't expect it to carry along VI properties.

[Darin.K]

I'd say not a bug, but rather it is an ill-defined operation.

Whereas a snippet does use a VI to transport code from one BD to another, the fundamental operation is to move the code itself, not any underlying settings from one VI to another.  I do not expect copy and paste of code from one VI to another to change any settings of either VI, and snippets are just adding a more persistent "clipboard".  In fact, I would argue it would be quite confusing if adding code to a VI changed these settings.

[Hooovahh]

Yup expected behavior.  If you wanted to share a VI then share that VI not the snippet.  But to be fair a VI is embedded in the PNG file so I'd be interested if the extracted VI contained these properties from the original VI.

[ouadji]

@ RavensFan

What is the property of the VI you are dropping the snippet into BEFORE you drop the snippet into it? 

A snippet is a portion of code, it isn't a VI in itself, so I wouldn't expect it to carry along VI properties.

Indeed, you are absolutely right.

I had not thought of this way of seeing things.

  +1