Short cut menu not available for control in a typedef?

[m3rl3n]

This seems strange to me.

I can create a control with a custom shortcut menu that works no problem when it is placed directly on the FP, but when I try to do the same for the same type of control when it is in a type def (three type def layers deep - but that is a long story) I only get the default shortcut menu. Even when I disable the menu option, I still get the default shortcut menu.

Does this mean that a control in a typedef can only use the default shortcut menu in its default state?

Thanks for any insight.

[Broken_Arrow]

I just tested this, and a custom shortcut menu works fine on typedef'd controls (in my case a chart). Maybe the shortcut menu is accessing one of your nested typedefs which does not have a custom runtime menu and that control's default menu is what shows up?

[m3rl3n · Accepted solution]

Hey Broken Arrow,

I am now getting back to this.

I know that I am going down to the lowest level of typedefs to the actual control itself, but your comment has me thinking......  and, yes, confirmed.

This is an inherited piece of SW so I was thought about something that has caught me in the past. Rather than the next lower level typedef control being placed in the next higher level typedef, a copy of a front panel control of it must have been copied so the inheritance was getting all messed up.  I completely redid the typedefs all the way through, which of course caused other problems, but they were fixable and it is all working great!! (for now 😉 )

SO, the answer to the question is yes, a custom menu CAN be added to a control even when buried deeply inside nested typedefs.