| Summary: | Using 0424-0010, I got org.eclipse.core.commands.common.NotDefinedException | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Olivier Thomann <Olivier_Thomann> |
| Component: | Debug | Assignee: | Michael Rennie <Michael_Rennie> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P2 | CC: | daniel_megert, emoffatt, Mike_Wilson, ob1.eclipse, pwebster, Tod_Creasey |
| Version: | 3.2 | ||
| Target Milestone: | 3.2 RC2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 135535 | ||
|
Description
Olivier Thomann
This is one possible cause for bug 135535. Raising severity. *** Bug 138241 has been marked as a duplicate of this bug. *** I believe this is a platform UI bug. The debugger creates contexts on the fly to manage view activation in the debugger (combines launch types and perspective). We can create contexts, activate and deactivate them from the IContextService methods #getContext(id) and #activateContext(id) (even if they are undefined). The service allows us to activate undefined contexts, so the platform should be allow for them when computing key bindings. (NOTE, we have been doing this for a couple months now, so something must have changed in the context manager/key binding code to expose this). I was planning on disallowing undefined context activations as part of fixing bug 135535. The fact they currently work is a bug, AFAIK, and they appear to contribute to keybinding problems. I have protected the BindingManager against undefined contexts for 20060424-0010 You can define the contexts using the Context#define(*) method. PW Fixed in PerspectiveManager. Please verify, Mike. verified. |