| Summary: | [EditorMgmt] Editor managment needs to resolve multiple 'default' editors | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | David Williams <david_williams> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bokowski, ccocchiaro |
| Version: | 3.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
David Williams
A solution I would prefer: Instead of defining default="true", it should be possible to define default="my.project.type.id". So a WTP XML editor could be the default for an WTP project and an other XML Editor could be default for the other XML files. ... I'm stuck in such a problem, too: I have a custom MANIFEST.MF Editor that can only proceed the manifest files located in a special project type -> I would need to enable the editor for a specific project type only. When I open an plugin MANIFEST.MF file, the default editor should then be used, not my custom one! *** Bug 167423 has been marked as a duplicate of this bug. *** Remy is now responsible for watching the [EditorMgmt] component area. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |