| Summary: | Key bindings don't work in Java editor | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Dani Megert <daniel_megert> |
| Component: | UI | Assignee: | Chris McLaren <csmclaren> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | CC: | eclipse, jcompagner, jfrantzius, markus.kell.r, mtim2000, pascal, trajano |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 41944 | ||
|
Description
Dani Megert
almost done.. *** Bug 41976 has been marked as a duplicate of this bug. *** fixed. the issue was that scopes (which are being phased out with the new 'contexts' api) currently no longer *automatically* follow the scope inheritance tree. i.e. java editor scope does not necessarily imply text editor scope. there is a use case (in debug) where we might need this. or we might not. (it is a case of A1 and A2 are children of A, and we'd like to set the contexts in the following order { A1, A2, A }. automatic inheritance would mean { A1, A, A2, A })
one fix would be to change the last line of of constructor to JavaEditor to:setKeyBindingScopes(new String[] { "org.eclipse.jdt.ui.javaEditorScope", "org.eclipse.ui.textEditorScope" }); //$NON-NLS-1$
i have added some temporary code to ensure contexts automatically imply their ancestors.
*** Bug 42016 has been marked as a duplicate of this bug. *** verified in I20030826-rebuild *** Bug 42077 has been marked as a duplicate of this bug. *** *** Bug 42081 has been marked as a duplicate of this bug. *** |