Show "Conflicts" if a VI cannot separate compiled code from source File

[TurboPhil]

The "Separate compiled code from source file" option is super nice for use with revision control software. However, sometimes the option to do so is not available:

This is usually because you have an express VI included somewhere in that VI's hierarchy. It would be nice to offer a means of displaying what those "conflicts" are--maybe a button to display a separate dialog, or to launch the search function with results of all the included Express VIs or any other potential conflicts. LabVIEW must know what those conflicts are--that's how it knows when to gray out the above option! So, how about a more detailed response as to why it has done so!

[Jim_Kring]

(+1) I agree.

[SMcGraw]

Thank you for your feedback.  I agree it is very useful to have this information.

[Darren]

The "Separate compiled code from source file" option can now be set on all VIs in LabVIEW 2012 and later, so there are no longer any "conflicts" to speak of.