Bugzilla – Full Text Bug Listing
| Summary: | [Key Bindings] Conflict of keyboard shortcut key (Ctrl+B) | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Kenji Uchida <uchi> |
| Component: | UI | Assignee: | Chris McLaren <csmclaren> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | asahata, Darin_Swanson, david_williams, nishino, paulacox |
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Kenji Uchida
If as proposed on platform-ui-dev, you plan to switch to Ctrl+Shift+B, the jdt debug will have to find something new for add/remove breakpoint. We need a larger alphabet. F2 still has CTRL+B as its shortcut key. Will you really change this on V2? This will not be changed. It was felt that too many people have become accustomed to Ctrl+B for build. Post 2.0, we should extend the key binding story to allow views to hook their own accelerators, and override the ones provided by the workbench. No-no. Ctrl+B bound to Bold function is a defact standard. You should avoid to use that for other purpose (such as Build), or Eclipse platform would so much abnomal in IDE's. Imagine that what users new to Eclipse (we expect so much more new comers than people accustomed to Ctrl+B for Build!) feel when they press Ctrl+B expecting Bold'ing function in PageDesigner but resulted in Build function. If I, I would be in panic !? A good user interface should not disapoint users' expectation. I would like you to please reconsider on this matter. I couldn't change the severity field. I think it should be "major". Our HTML editor has been using Ctrl+B as BOLD since the Eclipse V1 is released, and Ctrl+B as "Rebuild All" is newly assigned keyboard shortcut in Eclipse V2. (Actually Our HTML editor has more long history. It was released as a stand along product in several years ago, and Ctrl+B is always assigned as BOLD from the beggining.) However, Eclipse V2 is still not officially released. IDE should not breake pre-existing plugin's fuctionality. Our editor has had forced to change many of its keyboard shortcuts several times, when eclipse changed or assinged new shortcuts, but we don't want to change the Ctrl+B. Even if ctrl+B is common to current eclipse develpers, it should change the key to something else like Ctrl+Alt+B. Ctrl+B has been assigned to Build since R1.0. Note that it will not conflict if the autobuild preference is on, since we remove the menu item for Build All in that case. I confirmed that Ctrl+B as "Build" exists since Eclipse R1.0. We already know that "Rebuild All" is only available when autobuild is turned off. However, I still beleive IDE should avoid to assign such de-fact standard shortcuts (e.g. see Java Look and Feel Design Guidelines, appendix B) to another purpose. Ctrl+B is available for bold in the Text scope. Eclipse reserves Ctrl+B in the Global scope for build. Does this comment mean, standard shortcut key for "Bold" which is ctrl-B and Eclipse shortcut key for "Build" can't co-exist? Our editor needs *both* shortcut keys, and we don't want to use different key for "Build" shortcut key with other editors. What our users expect is both shortcut keys have standard key assignment on Eclipse environment. Ctrl+B will remain 'build' in the global scope. You can define a 'scope' for your editor, and you can add a keybinding Ctrl+B to mean 'bold'. Ctrl+B will be 'build' in all other editors and views, but be 'bold' in your editor. In your editor's scope you can also add the keybinding Ctrl+Alt+B for 'build'. When your editor is the active part, the menu will show Ctrl+B for bold and Ctrl+Alt+B for build. When any other part is active, the menu will show Ctrl+B for build. additionally, short of telling debug ui that they must give up their key (which i can't do), this is really a fix for the problem of conflicting keys. i should have marked this bug 'fixed' instead of 'wontfix' |