Script VI Properties Separate Compile Code option

[randoghsp]

The VI Properties General category has the boolean option "Separate compiled code from source file".  I would like to be able to set this through a script.  Is that option included in the scripting nodes somewhere?

We have many projects in SVN, none of their VIs have this property set so every time a minor change is made the result is a long list of VIs being added to the change list for commit.

[altenbach · Accepted solution]

Not sure about scripting, but if you open your project, there is a project option to mark all items, it will be applied the next time they are saved. Maybe that's all you need.

[santo_13 · Accepted solution]

Here is a simple VI that I put together (save in LV16)

[randoghsp]

Both options are perfect.  Thanks 🙂

[altenbach]

---

@santo_13 wrote:

Here is a simple VI that I put together (save in LV16)

---

I am curious if there is a reason why there are two loops instead of one?

[santo_13]

---

@altenbach wrote:

---

@santo_13 wrote:

Here is a simple VI that I put together (save in LV16)

---

I am curious if there is a reason why there are two loops instead of one?

---

Yes, I am ensuring all the files are loaded into memory before changing the property, thereby every VI need not spend time loading the same dependencies over and over again.

[randoghsp]

This setting is also available for control properties.  Should it also be set there or is that just a noop.

[altenbach]

---

@randoghsp wrote:

This setting is also available for control properties.  Should it also be set there or is that just a noop.

---

Not obvious. You could try both and compare the size of the *.ctl file. 😄