Bug 65906 - [KeyBindings] registry: Need way to define keybindings by OS, not by platform
Summary: [KeyBindings] registry: Need way to define keybindings by OS, not by platform
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks: 57290
  Show dependency tree
 
Reported: 2004-06-06 11:00 EDT by Dirk Baeumer CLA
Modified: 2019-09-06 16:11 EDT (History)
0 users

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 Dirk Baeumer CLA 2004-06-06 11:00:33 EDT 
I20040606

To fix bug 57290, which is marked as RC2, I need to define keybindings based 
on OS. Looking at the doc this is only possible per Platform (window system). 
Is there a way how I can do this ?
Comment 1 Douglas Pollock CLA 2004-06-07 09:16:53 EDT 
There are no plans to provide this facility in the 3.0 time frame.  The current 
solution is to define it for the corresponding widget toolkit.  For example, 
Motif would be used to change the key binding for Solaris. 
 
I agree this is less than ideal in the long run, as this also affects other 
operating systems (e.g., Linux). 
 
A fix for this would be to use "os.name" from the system properties as an 
additional filter.
Comment 2 Dirk Baeumer CLA 2004-06-07 11:03:35 EDT 
But there is nothing I can do to work around it ?
Comment 3 Douglas Pollock CLA 2005-02-21 13:50:03 EST 
I'll look at this for 3.1.
Comment 4 Michael Van Meekeren CLA 2006-04-21 13:14:44 EDT 
Moving Dougs bugs
Comment 5 Paul Webster CLA 2006-09-28 11:00:26 EDT 
There are currently no plans to work on this feature.

PW
Comment 6 Denis Roy CLA 2007-06-22 09:32:39 EDT 
Changes requested on bug 193523
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:11:16 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.