Bug 110031 - [KeyBindings] misc: replacement for CommandEvent.haveKeySequenceBindingsChanged
Summary: [KeyBindings] misc: replacement for CommandEvent.haveKeySequenceBindingsChanged
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2005-09-20 11:09 EDT by Tom Hofmann CLA
Modified: 2019-09-06 15:38 EDT (History)
1 user (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 Tom Hofmann CLA 2005-09-20 11:09:03 EDT 
3.2 preM2

The deprecated CommandEvent from o.e.ui.commands carried information about the
command's key binding having changed.

This info is not available in the non-deprecated version, nor from a different
facility (e.g. an IBindingListener that could be registered with the
IBindingService or similar). There is no way that an interested party (for
example a user affordance) can be notified when the key binding of the relevant
command changes.

Querying IBindingService#getActiveBindingsFor is not always an option:
- if the binding is displayed in a context other than where the user executes
it, e.g. on a preference page, getActiveBindingsFor may return nothing.
Comment 1 Tom Hofmann CLA 2005-09-20 11:58:44 EDT 
Dani, this will also affect a deprecation-free implementation of
AbstractInformationControl
Comment 2 Michael Van Meekeren CLA 2006-04-21 13:14:27 EDT 
Moving Dougs bugs
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:38:29 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.