![]() I've a few questions about Paul's comments: First, I'd like to inform you that I'm pretty rookie with e4 application model/framework, so excuse my comments if they seem dumb ) I'm trying to do some work on this issue. I'm not sure yet what to do in this scenario. However, if the contribution manager hasn't created a control yet, we aren't in a position to guess where we should hang the MMenu off of. Sometimes the views using this method for their own internal toolbars are not the active view. That provides the context for us to add the MMenu to. If the MenuManager (or ToolBarManager) has already created a control, then arguably we would walk up the parent chain, looking at getData(4.ui.OWNING_ME) until we find a model element. That information should be looked up/managed by the MenuManagerRenderer.Ģ) When it's time to add or remove an MMenuContribution or MToolBarContribution from the MApplication, MenuManagerRenderer (and ToolBarManagerRenderer) has to be able to add/remove ContributionRecord for the various managers.ģ) in populateContributionManager, you need to support a similar pattern for ToolBarManagerRenderer.Ĥ) in populateContributionManager, when you are looking for a place to put your MMenu, I think we have a problem. Bug231304Test.testToolTip()ġ) By keeping track of the MMenu to MenuManager, the MenuManagerRenderer is providing a link between locationURI (the MMenu elementId) and the MenuManager. ![]() Fails because of this bug and bug 365903 :
0 Comments
Leave a Reply. |