LabVIEW
"Save As" grayed out for Edited SubVI?
Solved!
The problem is that some of the system VIs are owned by a library (lvlib) which is locked. You can copy all code and paste into a new VI, then hook up all the connectors of the connector pane.
I have complained about that many times.
(Also make absolutely sure not to hit "save" in the modified original VI, else you'll mess up your entire LabVIEW installation, especially if the modified VI does not work correctly due to the changes)
@alexalexalexalex wrote:
Hi LabView experts,
This may be a dumb question, but why does the "Save As" option grayed out when I try to save a modified subVI? I tried to modified a LabView VI, and save it as a different copy so I don't overwrite the original one, but the option is grayed out. Any help or solution? Thank you very much!
You have to do some acrobatics to get this to work. Open your original VI. Click "Save As" and select "Open additional copy". This will prompt you to save the file, so have a file name in mind! Now close the original and there you go.
<snark>
Totally intuitive, right?
</snark>
I think it is this way so LabVIEW can keep track of the file and assign it to the right project and/or library.
I bet you opened the "Options" ( Tools>>Options Environment tab) and made these selections KUDOS!
Do not modify Examples or shipping items in vi.llb
I guess I missed the entire object of the post. I didn't realize the OP was trying to modify a VI that shipped with LabVIEW. I guess my auto-filter filtered out that tidbit of info because I only found one time when I ever did that, and that was because I wanted to add the error out to the connector pane of some file VI that didn't have an error output so I could handle errors that came out of it.
@alexalexalexalex wrote:
... the "Save As" option grayed out ...
@billko wrote:
... Click "Save As" ...
Hmm. Interesting. 😄
