Summary: | [ActionSets] Problem with ActionSets | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Anthony Hunter <ahunter.eclipse> |
Component: | UI | Assignee: | Douglas Pollock <douglas.pollock> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | tanakas |
Version: | 3.1 | Keywords: | Documentation |
Target Milestone: | 3.2 M1 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Anthony Hunter
2005-08-03 14:05:38 EDT
This is a question for the newsgroups. I asked a question to eclipse.platform a week ago, no answer. I believe this is either a bug or an undocumentated limitation of ActionsSets. "the location of the new menu starting from the root of the menu. Each token in the path must refer to an existing menu, except the last token which should represent a named group in the last menu in the path. If omitted, the new menu will be added to the additions named group of the menu." The key here is that the menu must exist. There is no dependency mechanism for action sets and we don't do automatic dependency detection. So, this leads to a situation where test2's action set can come into existence before test's action set. If this happens, then test2's action set will be found to reference a non-existent menu. You should take a look at Bug 36389, in particular Bug 36839 comment #9. Also, you might want to check out Bug 16282 comment #14, Bug 16282 comment #15 and Bug 16282 comment #16. Okay, I've added a note to this effect in the extension point documentation. Verified that this appears in the help. |