Separate Compiled Code missing for some VIs

[chrisb2244]

Some VIs do not have "Separate compiled code from source file" checked, which leads to the files being modified when opened on a different platform (I guess using 32-bit LabVIEW is not the norm here?).

I could easily change these and mark them all, but that will probably cause merge conflicts since the files might be in various unrelated places and then annoy everyone else trying to work in this repository :/

I'll add the checkbox to any files that I actually modify, but I'm opening the issue in case this repository has a period of time (e.g. releases?) when everyone is likely to not have open branches, in which case perhaps the files could be mass-ticked?

Alternatively, is there some preferred strategy for handling this? (Or are the files intentionally not separated from compiled code?)

AB#2972881

[navinsubramani]

@chrisb2244 I guess we all wanted to have the check box enabled for all VIs. I like your point about making the change when we want to change that VI for other purposes, and before the next release maybe @ccifra does the check for all.

Yes, Merging is a pain!

[jasonmreding]

Aside from testing related VIs, this should be fixed. The project used for editing the source is configured so that new project items will default to this setting and all existing items in the project have also been configured so that "Separate compiled code from source file" is checked.