LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV2009f2 vi corruption


pallen wrote: 
Perhaps that should have been a branch?  I'm really not sure. 

 

 


 

If you have the need to start work from an older revision make a new branch from that revision. Make a new working copy and work on that copy. Commit to this branch. After your work is done make a merge. Be aware that SVN is only able to merge VIs if you have set  the program LVMerge.exe from shared\LabVIEW Merge as merger for files with the extension VI. Otherwise it would just overwrite older files with newer ones. Unfortunatly I don't know of a good merger for the XML files .lvlib, .lvclass and .lvproj.

Waldemar

Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions
Message 11 of 13
(570 Views)

pallen wrote:

Been using TortoiseSVN since I started working at a new place.  (All the way across the street from the last place)

 

It's a great tool.  But I'm still going to be creating zip backups of every version before I commit.   I've run into a number of weird problems with Tortoise and if I hadn't had my backups I'd have lost quite a bit of work.  

 

 


As Waldermar mentionned...

 

I also agree and do the same as pallen.

 

I've got stories about how people abuse SVN and can create a bloody nightmare when multiple developers work on the same project.  It's so bad that it makes Local Variables look good..

 

Imagine many people checking out code and checking it in and being able to overwrite whatever was there previously.  Then two people editing the same VI because they are calling it from their own VI but need to adjust the behavior / change the connectors on the connector pane...

What do you get?

 

- sigh - 

 

As with anything, if you use a good tool the wrong way, you get a mess.  

Which is why I also do zipped backup which are dated.  That makes them unique and no one else can mess with them.  So far, it's worked well.

0 Kudos
Message 12 of 13
(554 Views)

Hi falkpl,

I have built a program using  LabVIEW 2011 version .  I was trying to edit my front panel without running the VI. During editing the vi( move the control or indicator to other place on front panel) my labview program became very slow. It was taking 8-10 sec to change. 

Also when I tried to save my vi it was showing the popup " LabVIEW:Cannot load Block diagram.  Cannot save VI test.vi" . Then I tried to close the VI and thereafter Labview become busy and not responding and shows the popup that "LabVIEW 11.0 Development System is not Responding" and finally my VI file get corrupted. Whenever I tried to open my VI, its shows the Popup "LabVIEW: Resource not found". File size of my VI was 1789 KB and became 912KB. I have attached my all error and popup.

 

Why my VIs are getting corrupted? 

Please help me to find the solution of this problem. 

 

Thanks

Srikant

0 Kudos
Message 13 of 13
(319 Views)