Home Community Idea Exchange LabVIEW Ideas Idea

LabVIEW Idea Exchange

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
egraham

Add option to auto-save class file (.lvclass) when a change is made to a class

Submitted by Member on ‎01-07-2022 10:04 AM 11 Comments (11 New)
Status: New

I want class modifications to be saved immediately. It's very rare that I need to revert any change I have made to a class.

 

One of the most time consuming tasks is fixing a class after I close and reopen it because I forget to [right-click > save > save]. In fact, I frequently make two source commits because I have forgotten to save the class and I don't realize until after I have made the first commit.

 

If not exposed through the options dialog, can we at least get a new LabVIEW.ini key?

 

autosaveClass=True

 

OR

 

saveClassOnChange=True

Labels:
11 Comments
AristosQueue (NI)
NI Employee (retired)
‎01-14-2022 08:37 AM
‎01-14-2022 08:37 AM

egraham: The only files that should be getting docmods in those cases are files where you did a rename of the dependency -- places where the callers must be saved or code breaks. LabVIEW is extremely conservative about docmods these days when source only is enabled. I would be very curious to see what you're tripping over. Honestly, we reached a point in LV2018 where we have seriously debated making source only be the only option for all VIs and just removing the option from the environment entirely, with some discussion of just auto-saving VIs on every edit (similar to what's being asked for here with classes). We decided not to do that, but our evaluation of our users' workflows and LV's behavior made us think we're there. So I'm somewhat doubtful about your claim -- did you do "List Changes" to see what changes were being saved and why LV decided those files needed docmods? (Docmods are the "document modification" asterisks that you see in the title bar when a file has unsaved changes.) I am not saying you're wrong, but I'd like to know a bit more in case there's some lingering issue we should be addressing.

 

My own personal testimony: I was a full-time G developer for 14 months (just came back to C++/G split role last week), and during that time, I used Save All almost exclusively instead of Save and, to the best of my memory, I had zero instances of excessive VI saving.

0 Kudos