[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ui-dev] Request for new Global Action on the Edit menu
|
I guess that explains why the Team Synchonize View doesn't use the Menu at
all.
You don't think that the Synchronize View is essentially an embedded tool?
And should be able to contribute Menu Items like "Next Change", "Copy Right
To Left", and "Refresh"?
Views seem to fall under 3 categories.
1) They are part of the Editor (Outline & PropertySheet).
2) They Open more Editors (ResourceNavigator, Packages, Project, Elements,
Members, Hierarchy)
3) They do their own thing.
I agree that #1 and #2 should not cause dynamic menu changes, but #3 is
different.
|---------+--------------------------------->
| | Nick_Edgar@xxxxxxx |
| | Sent by: |
| | platform-ui-dev-admin@|
| | eclipse.org |
| | |
| | |
| | 04/12/2002 10:01 AM |
| | Please respond to |
| | platform-ui-dev |
| | |
|---------+--------------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: platform-ui-dev@xxxxxxxxxxx |
| cc: |
| Subject: Re: [platform-ui-dev] Request for new Global Action on the Edit menu |
| |
| |
>---------------------------------------------------------------------------------------------------------------------------------------------|
Currently actionSetPartAssociations show the action set when the view is
opened, not when activated.
For editors, the action set is shown when the editor is frontmost.
Dynamic main menus are generally to be avoided, since the changes are not
visible to users.
This approach makes them more stable: the menus won't change their
contents (only enablement) when switching between views and the editor,
and when switching between editors of the same type. They may change when
opening/closing views and editors, or when switching between editors of
different types.
Nick
