Re: [framework-dev] Modifier keys (Mac OS X)

2009-02-16 Thread Robert Vojta
On Mon, Feb 16, 2009 at 12:39 PM, Mathias Bauer wrote: Hi, > What is the benefit of mapping CTRL to MOD1 on Mac? For whom is the > current approach confusing? Users never will see a "MOD1" anywhere and > developers should be able to cope with it. I discussed it off-list with Philipp and I'm tak

Re: [framework-dev] Modifier keys (Mac OS X)

2009-02-16 Thread Mathias Bauer
Robert Vojta wrote: > On 2/15/09, Maximilian Odendahl wrote: >> If you now change MOD1 to Ctrl on *all* platforms, this should still >> work as before. > > Probably my wrong description. Ctrl is already mapped to MOD1 on all > platforms except Mac, where it is Cmd. This should be changed as we >

Re: [framework-dev] Modifier keys (Mac OS X)

2009-02-15 Thread Robert Vojta
On 2/15/09, Maximilian Odendahl wrote: > If you now change MOD1 to Ctrl on *all* platforms, this should still > work as before. Probably my wrong description. Ctrl is already mapped to MOD1 on all platforms except Mac, where it is Cmd. This should be changed as we can define platform specific sho

Re: [framework-dev] Modifier keys (Mac OS X)

2009-02-15 Thread Maximilian Odendahl
Hi, MOD1 map to Ctrl on all platforms MOD2 map to Alt on all platforms MOD3 map to Cmd on Mac OS X if it is decided to do this, please make sure not to break anything. E.g. to insert a note on Window: Ctrl-Alt-N but on Mac, it should be Cmd-Alt-N If you now change MOD1 to Ctrl on *all

[framework-dev] Modifier keys (Mac OS X)

2009-02-15 Thread Robert Vojta
Hallo all, I've found that ... MOD1 is mapped to Ctrl on Linux, Windows, ..., Cmd on Mac OS X MOD2 is mapped to Alt on Linux, Windows, ... MOD3 is mapped to Ctrl on Mac OS X (added by me in macshortcuts01 CWS) ... it's confusing. I think that it was done in this way because Ctrl wasn't used f