|
From: Brian R. (JIRA) <no...@at...> - 2006-05-14 03:32:45
|
[ http://opensource.atlassian.com/projects/spring/browse/RCP-299?page=comments#action_17591 ] Brian Ross commented on RCP-299: -------------------------------- The create methods do return the component, however those methods are not called directly by the user's code, but rather internally within the framework during the construction of the main window. The return values are then discarded. Hence, there is no way for the user to get access to the menu bar or the tool bar. By having each command group hold a reference to the component it creates, it's easy to get a hold of it. In my case, from the LifecycleAdvisor I call window.getToolBar().getControl(). If you can think of a better way to accomplish this, I'm okay with that too. This way worked for me and seemed to fit in with the general Spring RCP achitecture as it is similar to the way views work, each one holding its control. > and access to the control on a CommandGroup > ------------------------------------------- > > Key: RCP-299 > URL: http://opensource.atlassian.com/projects/spring/browse/RCP-299 > Project: Spring Framework Rich Client Project > Type: Improvement > Components: Command System > Reporter: Brian Ross > Assignee: Larry Streepy > Attachments: CommandGroup.java > > some CommandGroup controls, like the toolbar, only support a very small set of features at this point. Those who wish to add things to the toolbar other than plain buttons need a way to access the control from their code. this involves only a small change to CommandGroup.java, which I will attach. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/spring/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |