Block diagram removed suddenly

[Zafer.Depe]

While I was editing splitters with "pane relief" add-on the VI became locked and block diagram removed suddenly. This is the second time I encounter such a problem. I immediately quit Labview without saving anything but the VI was automatically saved by itself. This behaviour occured after I upgraded to Labview 2023 Q3. This is a very risky (insane) situation for my big projects. I had no such issue with previous versions.

Is it possible to recover this VI and is there any way to prevent my files from such behaviours? I didn't save anything but the VI became unusable. Does "seperate compiled code from source file" option give additional protection for VIs? Also any idea if it is LV 2023 Q3 bug or the add-on originated.

[GerdW]

Hi Zafer,

---

@Zafer.Depe wrote:

Is it possible to recover this VI … ?

---

Generic answer: Pull an older revision of the VI from your SCC system!

[Zafer.Depe]

Seems I am very late to use a SCC software. Any advise for best Labview SCC integration?

[GerdW]

Hi Zafer,

---

@Zafer.Depe wrote:

Any advise for best Labview SCC integration?

---

I don't use any specific "LabVIEW integration".

I simply use TortoiseSVN for my project folders, others may suggest GIT or even other tools…

---

@Zafer.Depe wrote:

Seems I am very late to use a SCC software.

---

I started with regular backups of the development folders (aka "very cheap SCC tool"), then switched to SVN. Better start late then never…

[Zafer.Depe]

---

@GerdW wrote:

I started with regular backups…

---

I use OneDrive and sometimes it stops taking backups 😅 If I can spare some time to manage my project files I will switch to use SCC. Seems integration is not necessary. Thanks for advise.

[_T_M_]

One thing you can do is to stop Labview's autosave feature. Keep in mind this will affect autosave when you need it to work in normal situation.

Its in Tools>Options>Environment

I can see you have a broken Run button, but error does it report?

[JÞB]

For LabVIEW SCC integration I recommend TSVN and the TSVN Toolkit from Viewpoint ( which is actually a Framework.) Both are free. All of my Clients that chose to listen to me, have been happy with the choice.  Those who didn't listen wish they had.

[GerdW]

Hi Jay,

---

@JÞB wrote:

For LabVIEW SCC integration I recommend TSVN and the TSVN Toolkit from Viewpoint ( which is actually a Framework.) Both are free. All of my Clients that chose to listen to me, have been happy with the choice.  Those who didn't listen wish they had.

---

My colleague used to use TSVN integration, but when the SVN server is laggy (international company with SVN servers hosted in different countries) then LabVIEW IDE might become laggy, too. With last laptop change cycle he didn't install TSVN integration toolkit again…

I'm happy with my choice to handle SVN in WinExplorer.

[JÞB]

---

@GerdW wrote:

Hi Jay,

---

@JÞB wrote:

For LabVIEW SCC integration I recommend TSVN and the TSVN Toolkit from Viewpoint ( which is actually a Framework.) Both are free. All of my Clients that chose to listen to me, have been happy with the choice.  Those who didn't listen wish they had.

---

My colleague used to use TSVN integration, but when the SVN server is laggy (international company with SVN servers hosted in different countries) then LabVIEW IDE might become laggy, too. With last laptop change cycle he didn't install TSVN integration toolkit again…

I'm happy with my choice to handle SVN in WinExplorer.

---

Because the TSVN TK is a "Framework," the icon overlay refresh rate adds additional OS resources to LabVIEW Project Explorer. 

Giant, "Catch all" Projects are going to develop Laggy behavior only because YOU DIDN'T USE LVLIBS to develop your code modules!  That leaves YourProject managing a jiggilion poorly coupled files.  BAD programming practice everyday!

Then, toss in a few firewalls and variable/limited bandwidth between your Checkout folder and the SCC repository (Incompetent IT Managment!!!!) and your developer's are going to update their resumes.

[GerdW]

Hi Jay,

---

@JÞB wrote:

Giant, "Catch all" Projects are going to develop Laggy behavior only because YOU DIDN'T USE LVLIBS to develop your code modules!

---

I don't think you know our LabVIEW projects nor their content…