ContextMenu IsItemItsOwnContainerOverride

Owen,

Yes that is true because ribbon:ContextMenu inherits the standard WPF ContextMenu and we don't want standard MenuItem wrappers to be generated. Instead, you should probably include a ribbon:Menu as the child control of the ribbon:ContextMenu and bind to that.

Why not use GetContainerForItemOverride and provide your own subclass of MenuItem (or ribbon:Button given it already exists and is the most common use case for your stuff?)

[Modified at 04/02/2009 09:45 AM]

Owen,

We don't want any of the functionality that the standard MDI MenuItem introduces. Our ribbon:ContextMenu is designed to allow for direct inclusion of child controls without unwanted behavior that wrapping with MenuItem causes. This allows us to add things like the ribbon:Menu control and have complex layouts, while still allowing ribbon:ContextMenu to be used anywhere a standard ContextMenu can be used.

While we could have put ribbon:Menu functionality directly in ribbon:ContextMenu instead, as a design decision we chose not to because that would have prevented more complicated layouts as displayed in some of our QuickStarts.