Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 43851

Summary:	[KeyBindings] doc: Advise teams to not bind keys directly
Product:	[Eclipse Project] Platform	Reporter:	Douglas Pollock <douglas.pollock>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	minor
Priority:	P5	CC:	n.a.edgar, stori
Version:	3.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug
Bug Depends on:	31731, 46589, 48028
Bug Blocks:

Description Douglas Pollock

2003-09-29 14:04:23 EDT

Some pieces of code rely on keyCode being 0x00 when it is not longer ever 0x00.
 It would also be nice to encourage people to use the new key binding architecture.

Known classes with problems: DisplayView, BreakpointConditionEditor,
ProcessConsolePage, MessageConsolePage, and DetailFormatterDialog.

We should provide an email explaining the problem, describing the solution, and
encouraging users to use the new key binding architecture.  The email should
include snippets showing example usage of the key binding architecture.

Comment 1 Steve Northover

2003-09-29 15:16:34 EDT

There was something in the SWT release notes about this breaking change.

Comment 2 Douglas Pollock

2003-09-29 15:28:08 EDT

This leaves encouraging people to switch to using the new key binding
architecture, which is probably best to happen post M4.

Comment 3 Nick Edgar

2003-09-29 15:45:37 EDT

There are two separate issues here, as I see it:
1. Breaking API changes in Event.  These need to be cleared with Jeem and 
documented in the R3.0 porting guide.
2. Recommended changes to plugins to take advantage of the key bindings API, 
so they don't have to hardwire keys in key event listeners.  This is not a 
breaking API change.

Comment 4 Douglas Pollock

2003-12-02 12:21:39 EST

This is also dependent on key bindings being available in dialogs, I believe.

Comment 5 Michael Van Meekeren

2006-04-21 13:14:13 EDT

Moving Dougs bugs

Comment 6 Paul Webster

2006-09-28 15:12:50 EDT

Is this still a problem in 3.3?

PW

Comment 7 Denis Roy

2007-06-22 09:32:31 EDT

Changes requested on bug 193523

Comment 8 Eclipse Webmaster

2019-09-06 16:14:09 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 9 Eclipse Genie

2021-09-16 01:22:34 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.