remove block diagram support for multiple targets

[QFang]

Hi all, 

Have you ever wanted the security of "remove VI block diagram" but not wanted to deal with the "now I need n+1 copies of all my VI's" where n is the number of supported targets you need and the "1" is for your development source?

It isn't possible today, but take a moment and read/comment and maybe even up-vote this idea on the exchange: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/quot-Remove-block-diagram-ed-quot-VI-s-contain-compile...

then maybe one day... 

[QFang]

As Intaris commented on the idea exchange, this could also be what we need to prevent VI's for becoming "dirty" when you open them in a project for a different target (this causes a lot of unecessary comitts in an SVN system).

[Intaris]

On a counter-note I'm working on a VI to actually automatically revert such trivial "dirt" VIs when using svn.

I tested it yesterday and the basic functionality seems to work.  I need to test a bit and polish it up and maybe I can release it.  This would be a huge time saver for me when committing, not to mention doing away with a source of human error when cleaning up my local files before a commit.

Shane.

[QFang]

That tool sounds very useful, but how did you get around needing to rely on a user to filter real vs dirt changes? I'm assuming you are not automatically reverting every open VI, nor are you just doing an svn revert?  I'm intriged.

[Intaris]

There is a private method to do a LVCompare of two VIs.  It outputs if there are any actual CODE differences (Cosmetic, FP, BD etc.).

If the file is marked as changed by SVN but LVCompare says it's the same with the version in the repository, then it's safe to revert.

shane.