Access Scope Warning When Adjusting Mandatory Override Settings?

[Mr._Jim]

Hi all,

In my opinion, the access scope warning dialog should not appear when the user modifies mandatory override settings.

• Under "Class Properties" for a .lvclass
• Under "Item Settings"
• When modifying the settings of a dynamic dispatch VI
• If the user modifies one of the two checkboxes pertaining to mandatory override...

Regardless of whether the access scope actually changes, a warning dialog appears, and selecting "Yes" seems to cause the IDE to mark unsaved changes for other classes in the class hierarchy chain.  The warning dialog should not appear when all the user does is set the state of the two checkboxes, and to me it doesn't make sense that all of the other classes now have to be saved.  (I claim some ignorance on the saving part, though -  it's just my intuition.)

Does this make sense?

Thanks,

Mr. Jim

[AristosQueue (NI)]

This was consciously discussed when the dialog was added. We decided that it should appear. You may choose "no", but the option should be there. By setting the must override setting all the way down the tree, we felt we and our users would be less likely to introduce mistakes when refactoring to add or remove parent classes. There were times when this seemed like a good idea and so worth offering the option to automatically do it.

[AristosQueue (NI)]

PS: I'm totally open to changing it. I'm just explaining why it is the way it is today.

[Darren]

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.