Is it just me, or does save all not actually save all?

[billko]

---

@JÞB wrote:

---

@raphschru wrote:

---

@Intaris wrote:
Moving the Library in a virtual folder is NOT a real change to the library at all.

---

We are talking about moving a library member between different virtual folders within the same library.

I could reproduce the issue with LV2020-32bit:

The library can be saved explicitly if you right-click the library > Save > Save.

However neither "Save All (this Library)" nor "Save All (this Project)" actually save the library modification.

With LV2021-32bit, it asks to save the library when closing the project, as expected:

Regards,

Raphaël.

---

It relates to the context.  Since you only changed the lvlib within the context of a single lvproj the lvlib itself does not really accept that change.  This one reason why I ALWAYS create a project solely for each specific lvlib development!  Other reasons include: adding lvlib documents (Software Requirements, ReadMe.txt files etc...,) Unit Tests, Examples, build specifications,  basically everything that the lvlib DEVELOPER needs to deliver the library.   

In no case should the lvlib USER (often, other developers integrating the library into specific and diverse projects) be changing ANYTHING in any other context! Frankly,  that USER is working "Out of Scope" by attempting to change the library "Where USED" rather than "Where Controlled and documented."

I LIKE that the current behavior causes pain to the developer who forgets to change context!

Plus, the current behavior permits CONCURRENT development of both the lvlib itself and, the using project(s)!

I understand this choice by NI might be considered undesirable by "lone wolf" developers that are not using  rigorous software development practices.  However,  this exact behavior is essential!  Just imagine how many times it saves "careless developer of calling project A" from the pain caused when the developers of calling projects B-Zz gang up and give him a good beating for forcing inappropriate changes to those several projects!

I guess a better analogy would be to ask if you would walk into your local public Library a feel comfortable moving the Bible from non-fiction Dewey Decimal 000.xxx to a shelf in Fiction?  Would you choose G for God, C for Council of Nicea...? And, how would you reflect that change for every other library with a copy of that work,

---

I have to say you're still missing the point.  The point is that it simply isn't saving the changes you made.  As defined in that nice little animated GIF.  And apparently it was fixed to work the way I expect it to in a later version.