Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 57052 - [KeyBindings] F11 (Debug Last Launched) Conflict on MacOS X
Summary: [KeyBindings] F11 (Debug Last Launched) Conflict on MacOS X
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.0   Edit
Hardware: Power PC Mac OS X - Carbon (unsup.)
: P2 normal (vote)
Target Milestone: 3.0 M9   Edit
Assignee: Darin Swanson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-01 10:47 EST by Douglas Pollock CLA
Modified: 2004-05-10 20:15 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Douglas Pollock CLA 2004-04-01 10:47:58 EST
Unfortunately, the standard keyboard configurations conflict with OS-defined 
keys.  The Debug Last Launched key (F11, in the default keymap) is taken by OS 
X v10.3.3 as the key to display the desktop).  The M7 updated "Standard (3.0) - 
NEW!" keymap had mapped this to Cmd-D, Cmd-D, which was convenient and does not 
kick in operating system functions.  The various text navigation keys defined 
in Eclipse drastically clash with those defined in native OS X applications 
(beginning of line, previous word, select until end of line, etc).  This makes 
any sort of keyboard editing extremely counter-intuitive to intermediate and 
advanced OS X users.
Comment 1 Douglas Pollock CLA 2004-04-01 10:48:58 EST
I will investigate for M9. 
Comment 2 Darin Wright CLA 2004-05-04 14:05:56 EDT
Doug should we just assign this to another key on the Mac?
Comment 3 Douglas Pollock CLA 2004-05-04 14:12:16 EDT
I will say again that binding function keys is frowned upon by Platform UI. 
That being said, you have two options.  The best option is to move the key on 
all platforms.  If this is no desirable, then yes, you should move it on MacOS 
X. 
Comment 4 Kevin Barnes CLA 2004-05-05 13:03:42 EDT
changed mapping from "F11" to "Command+F11" on mac.
Comment 5 Kevin Barnes CLA 2004-05-05 13:04:34 EDT
change in debug.ui/plugin.xml
DarinS, please verify
Comment 6 Douglas Pollock CLA 2004-05-05 13:36:38 EDT
Doesn't this conflict with run last launched? 
Comment 7 Darin Swanson CLA 2004-05-05 13:38:11 EDT
I believe Doug is correct...in comment #6
Comment 8 Darin Swanson CLA 2004-05-05 13:43:38 EDT
Actually it does not conflict currently as on the carbon Ctrl-F11 is run last 
launched...but on the mac it should be Command-F11?
Comment 9 Kevin Barnes CLA 2004-05-05 14:02:55 EDT
It doesn't conflict, but it is kind of wonky. I did it this way to try to keep 
it similar to other platforms. Maybe "Command+F11" as debug and "Command-Shift-
F11" for run would be less confusing for users?
Comment 10 Douglas Pollock CLA 2004-05-05 14:15:54 EDT
In general, "CTRL" should not be used in key bindings on MacOS X.  The only two 
exceptions I know of are terminal escape sequences and Emacs key bindings. 
 
Here's a little trick to help you out.... 
 
M1 = CTRL/COMMAND 
M2 = SHIFT 
M3 = ALT 
M4 = Platform-specific fourth key 
 
You can use "M1+F11" when you want to define "Ctrl+F11" on Windows/Linux, and 
"Command+F11" on MacOS X. 
 
Again, I'll say that function keys are not advisable.  On KDE, for example, 
Ctrl+F11 means "Switch to Desktop 11".  If you still like your function keys, 
then Kevin Barnes' suggestion in comment #9 sounds good. 
Comment 11 Kevin Barnes CLA 2004-05-05 17:01:20 EDT
remapped debug last to "Command+F11", and run last to "Command+Shift+F11".

Did not use M1, M2, M3 because I didn't want to affect the windows keybindings at all. Windows is 
quite happily letting us use F11 and I don't see the need to inconvenience users that are comfortable 
with the existing keybinding. Also M(1,2,3)+F11 all gave me "Shift+F11" functionality instead of Crtl, 
Shift and Alt (tested on Windows). Is this a known bug?
Comment 12 Douglas Pollock CLA 2004-05-05 17:12:59 EDT
We use "M1+M2+W" for "Close All", and it works as expected.  So, I'd guess ... 
no, it is not a known bug. 
Comment 13 Darin Swanson CLA 2004-05-10 20:15:10 EDT
Verified.