Cannot save edits to VI

[Reclined]

I opened the Evaporative Cooler example to have a look, and have bumped up against something seemingly basic that doesn't seem to work - in the application launcher lvlib, there's Localization.VI where you can change what appear on the splash screen. I can change the contents, and if I run the app with the vi still open, I can see the changes, but it's opened the vi read only, and I cannot find where to make it so I can actually save my changes.

Any ideas appreciated!

It's not in run mode, and it's unlocked in the protection properties.

Thanks

[billko]

---

@Reclined wrote:

I opened the Evaporative Cooler example to have a look, and have bumped up against something seemingly basic that doesn't seem to work - in the application launcher lvlib, there's Localization.VI where you can change what appear on the splash screen. I can change the contents, and if I run the app with the vi still open, I can see the changes, but it's opened the vi read only, and I cannot find where to make it so I can actually save my changes.

Any ideas appreciated!

It's not in run mode, and it's unlocked in the protection properties.

Thanks

---

If this is an NI example, I recommend NOT changing the example.  Instead, copy the project somewhere and work on that.  You want to leave the examples pristine.

I couldn't find the example, so I can't tell you what might be wrong.

[altenbach]

Yes, don't mess with shipping VIs!

Does this example come from a specific toolkit? Which one?

Maybe the lvlib library itself is locked?

[Bob_Schor]

---

@Reclined wrote:

I opened the Evaporative Cooler example to have a look

---

Is this, by any chance, a sample/demo Project for Actor Framework?  If so, you might get more notice by including "Actor Framework" in the Title ...

Bob Schor

[Reclined]

Yes sorry, it is the Feedback Evaporative Cooler project template, which is based on the actor framework. It's one of the templates presented as a choice on a new installation of 2017, and when you open it, it asks for a new name to create a copy, so you're not messing up the original.

[Bob_Schor]

I recall struggling with that 5-6 years ago (when I had a little more "free time").  Of course, right after Actor Framework was introduced, Asynchronous Channel Wires were being developed, and I got involved with some of the pre-release testing, and have been using them ever since.

If memory serves, wasn't there a "completed" version of the Demo included that you could run when you couldn't quite get all the Puzzle Pieces to fit in the right order?  But don't worry, now that Actor Framework is in the title, other "Actor" actors will probably offer useful suggestions.

Bob Schor

[Reclined]

Thanks, Bob.

It doesn't seem to be a general issue with the framework, just this particular VI. I haven't thoroughly checked through, but it's the only one I've seen in the project behave like this.

There is another localization.vi under Application/Chamber Environment Application.lvlib/Chamber Environment Application.lvclass which likewise seems to open read only, but behaves slightly differently - If I edit then close the first one, changes are lost, but when I close the second one, changes are onnly lost when I close the project.

[altenbach]

---

@Reclined wrote:

Yes sorry, it is the Feedback Evaporative Cooler project template, which is based on the actor framework. It's one of the templates presented as a choice on a new installation of 2017, and when you open it, it asks for a new name to create a copy, so you're not messing up the original.

---

Are you sure that if you create a copy of the project that it will also create a copy of the lvlib? I would not assume that it does. You can check the location to make sure.

[Reclined]

altenbach, it is in the project folder, not a shared file