Block diagram removed suddenly

[billko]

I find that disabling auto-refresh removes most/all of the delay.  Just refresh the icons when you need it to and you'll be fine.

[JÞB]

---

@GerdW wrote:

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…

---

Oops,  that is the danger of replying on a globally relevant forum (you can accidentally insult other posters.)  There was no intention to critique any one specific team's code base.  The criticism used "You and Your" pronouns to mean the general population of code developers.  My reply quoted you to show it addressed the reasons TSVN TK can appear laggy rather than address the original topic.

The best tools for any task can become problematic if the task itself is poorly designed and supported or even when the scope of the task is greater than the tool's intended use. (The best framing hammer won't help assemble a cinder block foundation.)

[billko]

---

@JÞB wrote:

---

@GerdW wrote:

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…

---

Oops,  that is the danger of replying on a globally relevant forum (you can accidentally insult other posters.)  There was no intention to critique any one specific team's code base.  The criticism used "You and Your" pronouns to mean the general population of code developers.  My reply quoted you to show it addressed the reasons TSVN TK can appear laggy rather than address the original topic.

The best tools for any task can become problematic if the task itself is poorly designed and supported or even when the scope of the task is greater than the tool's intended use. (The best framing hammer won't help assemble a cinder block foundation.)

---

Hence "Y'all".  (Seriously.)

[tst]

A few comments:

1. I agree with the others that SCC is highly recommended. This doesn't just fill the simple role of having a backup, but also let's you maintain a history with comments of what you did, go back through that history, keep the code synchronized with multiple machines, etc.
2. SVN works well and is simple and you don't need the LV integration. You can get started with having the server on your own computer, but then you should make sure you have regular backups of the SVN repository to somewhere else. You should do that even if the server is not on your machine if you care about being able to recover your code.
3. Assuming your OneDrive backup doesn't let you get your VI, you could also try the standard Windows backup. Right click a folder or a file and select Restore previous versions. This isn't guaranteed to work or get you what you want, but it's an option you can check.
4. I don't know why the problem you're describing happened, but I'm assuming Pane Relief doesn't have any code for removing the BD or for saving the VI. I suppose it's possible that it is corrupting the VI somehow. I think it does have some tricks for creating zero-pixel splitters. In any case, the auto-saving mentioned in another reply shouldn't be the cause of this, as that saving is not supposed to overwrite the original VI. It saves a copy in the LabVIEW Data folder, so LV can recover it in case of a crash.

[Zafer.Depe]

Fortunately I have a recent backup and restrored the VI immediately. Then I did some extra tests and I got details below;

1. This behaviour occurs each time when I try to resize a zero pixel splitter.
2. The VI is executable. But cannot editable anymore (also front panel is not editable).
3. VI acts as a build distribution and the file size increased enormously.
4. The VI has many splitters.
5. There are some objects fitted to panes and auto size active.
6. When I put a splitter to a new created VI, add-on works properly.
7. When I remove auto sizing property of fitted objects, behaviour disappears. VI still usable. But the add-on still cannot resize the splitters but throws errors.
8. I copied BD of the VI and pasted to a new created VI. All splitters are removed. Seems there are no errors yet. But I will redesign the front panel and try to use the add-on again. I will add if I have more information.

[Zafer.Depe]

9. After recreating the front panel, add-on still makes the VI uneditable, independent of the splitter's pixel size. Be careful while using this add-on with LV 2023 Q3.