Bug 94507 - [KeyBindings] preference page: Warn when defining multi-key that clobbers single key
Summary: [KeyBindings] preference page: Warn when defining multi-key that clobbers sin...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P5 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 138683 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-05-10 16:12 EDT by Matthew Conway CLA
Modified: 2020-04-06 16:56 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Conway CLA 2005-05-10 16:12:51 EDT 
The platform key binding UI allows me to define a new multi-key binding with the
same "start" key as an existing single key binding.

e.g. define "Ctrl+S Ctrl+A" to "File->Close All"and Ctrl+S no longer works for
saving

I'm not sure if a multi key binding can coexist with a single key binding in
this way (timeout after first key press?), but at the very least maybe the UI
should warn (or prevent) me when I attempt to define a multi-key binding that
starts with an existing single key binding.

eclipse 3.1M6 on linux FC2
Comment 1 Douglas Pollock CLA 2005-05-11 08:39:09 EDT 
The effect of clobbering the single key is intentional.  I agree that a warning
about this would be nice.
Comment 2 Michael Van Meekeren CLA 2006-04-21 13:14:42 EDT 
Moving Dougs bugs
Comment 3 Paul Webster CLA 2006-09-28 15:14:46 EDT 
Is this still a problem in 3.3?

PW
Comment 4 Denis Roy CLA 2007-06-22 09:32:55 EDT 
Changes requested on bug 193523
Comment 5 Markus Keller CLA 2008-04-10 06:52:57 EDT 
*** Bug 138683 has been marked as a duplicate of this bug. ***
Comment 6 Eclipse Webmaster CLA 2019-09-06 15:36:04 EDT 
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.
Comment 7 Rolf Theunissen CLA 2020-04-06 16:56:56 EDT 
*** Bug 552151 has been marked as a duplicate of this bug. ***