| Summary: | [KeyBindings] preference page: adding keybinding removes keybinding from more specific context | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Randy Hudson <hudsonr> | ||||
| Component: | UI | Assignee: | ali sheraz <ali_sheraz> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | pwebster | ||||
| Version: | 3.1 | ||||||
| Target Milestone: | 3.3 M7 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 176235 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Randy Hudson
Moving Dougs bugs Is this still a problem in 3.3? PW yes Created attachment 64811 [details]
Binding Manager v01
The code that was supposed to build a list of all keybindings would remove any SYSTEM keybindings that it found first.
PW
I recently re-encountered this bug and nearly opened a dupe of myself. The reason this is so annoying is that the conflict is often assumed but doesn't really exist. The example mentioned here already shows thi. "Go Into" is never enabled at the same time as "Next Word", yet the preference page assumes a conflict based on context inheritance, and re-maps the existing binding. Already in I build. PW Does the solution also handle the scenario where the two contexts are orthogonal? Now adding a keybinding will only remove the system keybinding with the same command in the same scope. PW In I20070501-0010 PW |