Bug 309092 - [Commands] Unify hotkeys for all platforms
Summary: [Commands] Unify hotkeys for all platforms
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2010-04-14 06:08 EDT by Dmitry Nezhevenko CLA
Modified: 2019-09-06 16:04 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Nezhevenko CLA 2010-04-14 06:08:37 EDT
Build Identifier: I20100129-1300

During development on Mac and PC at same time, it's sometimes very annoying to remember Control/Command differences between them. 

It will be really cool to have some way/checkbox to swap Control and Command on Mac for hotkeys so that, for example, Ctrl+Shift+R will show "Open Resource" dialog on both platforms.  

Reproducible: Always
Comment 1 Eric Moffatt CLA 2010-04-20 16:09:46 EDT
There may be reasons for this not to so (platform conventions that either have a standard binding or a standard binding that is the same as one of ours). I'll pass it on for further comment.
Comment 2 Dmitry Nezhevenko CLA 2010-04-20 16:23:41 EDT
Thanks. I understand that this may conflict with platform HIG's. That's a very good reason to have this option turned of by default (or even hide it to some advanced section). 

As about conflict with some global hotkeys, even default eclipse hotkeys conflicts with them. For example by default all "F1-F12" keys on Mac are mapped to some global actions (like switching spaces, etc). Lucky we still have way to disable such global shortcuts in OS.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:04:47 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.