I found some workarounds. We can create a IWorkbenchWindowPulldownDelegate2 action, that has dynamic submenus. And also with the selectionChanged(IAction action, ISelection selection) method of the same interface we can have access to the proxy action that is behind our actionset and we can action.setText(..) to change it's name. The thing with this is that we must make sure that selectionChanged(..) is called before the user sees the action.
So, I think this solves our problems with the menus/toolbar. Back to work, :) On 9/19/06, Bogdan Ciprian Pistol <[EMAIL PROTECTED]> wrote:
:), I was wrong on the hiding/showing ActionSets. They have IWorkbenchPage.showActionSet(...) and IWorkbenchPage.hideActionSet(...) So, I still have issues, but at least this one is solved. On 9/19/06, Bogdan Ciprian Pistol <[EMAIL PROTECTED]> wrote: > Hello, > > I investigated the menus & toolbars and my conclusions are: > > We want to integrate the ArgoUML menu/toolbar within Eclipse. This is > already accomplished, but the menu is only active when the editor is > active. > This contextual approach would be good but, we use Swing inside SWT, > so because of this when we click in the Swing JPanel inside the SWT > Eclipse Viewer, the JPanel is focused and reacts but it's possible > that the SWT Viewer doesn't become active. > > So there are other options beside actions dependent on the editor: actionSets. > The issue with these is that you can't hide them or show them or even > change dynamically their text. > Here https://bugs.eclipse.org/bugs/show_bug.cgi?id=26593 and in the > Eclipse FAQ they say that you can't have dynamic top-level menus (only > submenus) and these can't be hidden or shown dynamically. > > There are some not very nice solutions like using a static top-level > menu and all the submenus be dynamic or maybe try to control the Swing > to synchronize with the SWT when it catches focus, or add local > views/editor menus (inside the editor/views) > > I consider this a priority, because the user can be easily confused by > the actual appearance of the menu/toolbar. > > I will investigate further and try to come up with a solution. > > As a result of this I excluded the actual implementation of the > DiagramActionBarContributor and no menu is available temporarily. > > In rest all the refactoring is done. > > Bogdan >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
