| Summary: | After startup the Mac Os system shortcuts do not work in Eclipse IDE. | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Roman Knoell <mail> |
| Component: | IDE | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | Keywords: | helpwanted |
| Version: | 4.2.2 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X | ||
| Whiteboard: | stalebug | ||
|
Description
Roman Knoell
Eclipse doesn't create the menus until the first time the user shows them (to avoid excess plugin loading). When they are shown, osx instantiates them and that's why they work from then on. Eclipse shortcuts are managed from Preferences>General>Keys. PW Saying that Eclipse software doesn’t care about the operating system it is running on – ignoring the whole environment – is not a resolution of its FAULTY behavior IN the respective environment. There might be a way to handle shortcuts otherwise, e.g. to auto-adjust the internal Eclipse settings with respect to the global , and thus more general, operating systems settings. I don't believe so, as the behaviour you are talking about is not exposed to us it's handled completely in the operating system, and auto-instantiating every menu (with it's attendant performance and memory consumption costs) can't happen. Eclipse has a shortcut management system, and I see only confusion in trying to add another one that depends on specific widgets being instantiated. But we would consider a patch (you'd probably have to start at the SWT level). http://wiki.eclipse.org/Platform_UI/How_to_Contribute PW 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. If the bug is still relevant, please remove the stalebug whiteboard tag. |