Prompt to Save Type Def when Creating from a Constant or Control

[AustinManinTown]

LabVIEW 2011 allows you to 'Make a Type Def' by right clicking on a control, indicator, or constant. What new users don't realize is that the type definition has to be saved as a custom control. The current save method and prompts are not very clear. Maybe it would be better if the developer is prompted straight after the creation of a type definition to save the .ctl file. This would make it clearer that there is a connection between the type def. and the .ctl file.

[AristosQueue (NI)]

This idea was considered and explicitly rejected in the design of the new feature. Typedefs are not normally for new users and more experienced users were frustrated by having to deal with the save dialogs right then and there.

[AustinManinTown]

LabVIEW Core 1 students are taught the benefits of using typedefs as a mechanism for managing data definitions. The confusion I see, with students, is that they don't fully appreciate that the custom control has to be saved and are further confused/overwhelmed when presented with a number of save dialogs when saving the VI.

To address the needs of more experienced users, there could be an option to disable the save typedef until the VI is saved.

Maybe it is time to separate custom controls and data definitions and use the term 'custom data types', as is done in TestStand. Custom Controls infers a change to the look and feel of a front panel object. Educating new LabVIEW developers to use typedefs as a means of managing data could be made easier if it was clear what the function of the typedef is.

[SteveChandler]

I think the way it behaves is kind of confusing especially if I made seven things into typedefs. I get a dialog asking me to "Name the Control (Control 5)" but I don't know which one it is refering to. I have not used the new LV2011 feature yet other than to play around with it while it was in Beta. I have not used it since the release.

I always explicitly create controls by right clicking the library it belongs to and selecting new control. That gives the advantage that the starting path is the same as the library and it automatically inherits the icon of the library. To me the new 2011 feature is not very useful at all.

[AustinManinTown]

Without wishing to put words into your mouth, Steve here is how a read your post. As an experienced developer you find saving typedefs with the vi save confusing, as it is difficult to know which control is which. To solve this you create typedef controls in a project library as a method of managing their creation and location (neat solution).

I am going to conclude that the LabVIEW 2011 method of creating and saving typedefs is ripe for improvement, as no one is happy. New users are confused as they don't see a relationship between a custom control (typedef) and a bunch of file dialogs. Experienced users see the relationship, but don't know which typedef is which. My vote is to make it easier for the new users and recommend, Steve's method for experienced users.

[SteveChandler]

What I am saying is that if you use the new 2011 feature to make several controls into typedefs then when you go to save them it is going to be confusing. I don't use libraries as a workaround for this. In my projects everything is in a lvlib except for the top-level vi. All I am saying is that it is a better to create the typedef up front, and right clicking a library has several advantages.

I think the new feature should be looked at as a fallback method for situations where you realize the constant (or control) should have been a typedef to begin with. It is more cumbersome for both new users and experienced users than just explicitly creating the typedef in the project explorer one way or another.

I put this feature in the same catagory as the feature to make a selection of code into a subvi. New users should not even be taught about either of these or they may think of them as the primary method of creating the files.