Forced Recompile Fixes Problem

[niNickC]

Hello,

So I have been developing LabVIEW on and off for a while now. About 7 years.

For the first time yesterday I had a problem where a forced recompile fixed the problem.

I started seeing some very bizarre behaviour (code only part executing, breakpoints stopping but unable to restart execution etc).

I did ctrl-shift click on the top level run arrow, one sub VI call broke (It went 'missing' with ? icon) and after fixing this the code executed correctly.

This is obviously a bit worrying. The project is actually quite hygienic too (I prehaps could forgive LV if it was a mess of dependencies...)

I'm interested in hearing if anyone else runs into this kind of problem? If so how often? 

I'm not sure what more information I can give but maybe I am doing something wrong.

Thanks!

note: I do use source code control and the next step would have been a roll-back so no major stress but still...  

[bseguin]

I saw this kind of issue when a VI has been renamed or mover outside LabVIEW and then LabVIEW reopen with this VI. This is not alarming if this is the case since there is no corruption of vi or whatever. Make sure that if you plays around with the name or the hierarchy of the VI path, you do it inside LabVIEW, or a recompile/save all this library could be necessary.

If the reason is hard drive corruption, a recompile might not save the day...

Benoit

[billko]

In case you are having the dilemma of moving in LabVIEW and resolving in SCC or moving in SCC and resolving in LabVIEW, I think the former solution is much easier to deal with than the latter.  At least it is with SVN (with TSVN interface).