"Save and close after saving" option in Create Accessor dialog

[Ljubo]

Hi!

I usually access class data members through property nodes. Create Accessor dialog is a useful tool for creating accessors but it really became annoying to close and save accessors manually. What I suggest is an option in Create Accessor dialog. If checked all accessors will close after creating process without opening the file save dialog.

There is already a similar tool which works nice: Actor Framework Message Maker.

[Manzolli]

Did you mean "Save and close after creating"?

[Ljubo]

Manzolli,

the result is the same.

Regards, Ljubo.

[Manzolli]

OK, but it is, at least, an awkward phrase.

[AristosQueue (NI)]

What would folks think if I just made that the behavior instead of adding a checkbox? I could do the zoom highlight on the project tree for people who wanted to open them. This is exactly the sort of thing that makes a bad option -- it clutters the dialog with an option that isn't directly related to configuring the property, which is the task at hand. In that respect it is "off topic" from the rest of the dialog. It is better to just pick a behavior. Would just creating the VIs but not opening their panels be a better behavior for most uses?

[tst]

I would say open just the FPs and save (in the same folder as the class, or maybe the dialog does need a another control for relative path). That way, at least closing the FPs is relatively quick and easy (Ctrl+W, repeating, assuming LV didn't decide to shuffle our windows). I say that because I do think that some editing (icon, documentation, input validation, etc.) is sometimes needed and this makes it less likely to be forgotten.

[Intaris]

I would like them closed automatically.

I would also, however love to have a class browser where all VI Icons for different functions were visible, but that's a different story.

[Ljubo]

I vote for:

- save after creating

- behavior instead of checkbox

- open FPs, as tst suggested. Using Ctrl+W is fast enough.

[AristosQueue (NI)]

Save after creating generally has gotten lots of panning... seems people like to create classes and multiple VIs in those classes and then be able to throw everything away. I've wanted to do "class automatically saves on creation", but I get push back, but it's mixed feedback to decide how strong that feedback is. And I have many times created accessors only to decide, no, I didn't really want those accessors, and throwing them away without them having been saved is nice, so I see where they're coming from.

When I asked my question earlier, I was thinking I could just not open the panels -- the classes would hold the accessors in memory until you decided to do Save All.

Another issue that came up today -- if I were to auto save the accessors, shouldn't I also autosave the entire class so that we don't end up with class and VIs out of sync with each other? That's something that I have heavy numbers of people asking for -- make it impossible to save a VI that has just joined/left a class/library unless the class/library is saved at the same time (and, vice versa, make it impossible to save the class/library unless you save the VI at the same time).

(I'm asking these questions because even though I no longer work on LV classes directly, this code is in G and is something I might could tweak in my spare time. No promises, but I like to have projects in my backlog in case I get spare moments.)

[tst]

Save or Save Not, there is no try.

Sorry, I think my mind was elsewhere. Personally, I would probably prefer not to save (since I don't like LV saving things automatically in case I changed them and then want to revert). I would manage with the case where I did not save and would now have to realize that and re-add the VIs manually.

[fabric]

Personally I find the current behaviour to be slightly clunky but I don't want auto-save and I don't want my panels closed either. Why?

• I generally modify all my read accessors (remove the obj out)
• I generally add one or two words to my icons
• I generally edit the default names
• I sometimes need to modify reentrancy or inline-ness

This has helped quite a bit, but in the end I find it easier to have the panels there.