saving a vi

[marino]

Hi,

I'm having a small problem with saving a vi.
I added a small peace of code to an existing vi without changing the vi properties or adding variabeles, terminals,...
When I save this small change, all the vi's that use this changed vi also needs to be saved! The problem is that I use source safe to manage my software, so I need to check in an check out all the files that use this vi. But I want to know the reason for this.
So, I searched what the problem was and it had to do with the error clusters. I only changed the position of the 'error out' cluster and when I do that, all the vi that use this vi must be re-saved. When I leave this error out cluster were is originally was, the vi's who call this changed vi don't ask me to save them.

Is th
is normal?
I'll attach an word document to this mail with a print-screen of the position of the error clusters (how I changed them).


thanks in advance,

Kind regards,
Marino

[Evan]

When you are changing the position of the error out cluster how are you doing it? Are you deleting the original cluster and then creating a new cluster on the other wire? Or are you just deleting the wire to the terminal and then moving the error out terminal and re-wiring it?

If you are deleting it and then re-creating it, then the connector pane of the VI will have changed. When you deleted the error out terminal it will remove the indicator from the connector pane. LabVIEW will not read the new error out cluster to the connector pane.

[beeuwke]

Hi,

Thank you for the response...

I don't delete the error cluster. I delete the connection to it and then move it. I leave the terminals alone. I only added some functionallity to the vi without changing terminals.
Normally the vi's that call the changed vi's should not be asking me to be saved if you don't change the terminals of the subvi, or am I wrong about this?

kind regards,
Marino