Preserve custom run-time shortcut menu when replacing control (at least when control is of same type)

[Mads]

If you have made a custom run-time shortcut menu and saved it as part of the control (always necessary for applications due to this issue), it is currently way too easy to lose that menu. If you replace the control, even though it is with the same type of control, the menu is silently lost. So if you have made right-click shortcut functionality, the user will no longer be able to call that funcitonality.

Possible solutions:

a. As a minimum you should be warned that the control you are about to replace has an embedded shortcut menu.

b. The warning could give you the option to copy the menu to the new control (OK set as default), or

c. The new control could automatically inherit the original's shortcut menu

d. -Alternatively only if of the exact same type (if you for example replace a modern styled listbox with a system style listbox).

I would prefer alternative b, as it would draw the developer's attention to the possible issue of the embedded menu (perhaps it is *not* wanted anymore, perhaps it is...), but make it quick and easy to choose to keep the menu (most frequent I would guess).

[Mads]

Note that this idea is also applicable in cases where the menu is saved as a separate file, but the problem is lessened in those cases by the fact that then you at least have the option to relink the control to the menu (hopefully you remember to do that right away...). You do not have to recreate the menu.

Now one of the reasons people often save the menu as part of the control instead though is the bug t...

[X.]

 Give NI another 8 years (at least) to think about this one...