On Mon, Sep 14, 2009 at 1:39 AM, Eike Ziller <eike.zil...@nokia.com> wrote: > Am Sep 13, 2009 um 11:19 AM schrieb ext Shawn Rutledge: > >> I'm mostly enjoying Creator. But here's a couple things that drive >> me bonkers: >> >> On MacOS, by default there is an incompatible/unexpected mapping for >> home/end keys, across the OS. It can be fixed for some (most?) apps >> like this: >> >> http://phatness.com/node/1661 > > Ah, how I like this kind of ranting ;) > Actually it's equally annoying to move to e.g. a Windows machine if > you are used to work on a Mac. > I speak from experience, though it usually takes me only a few minutes > now to adapt to the OS (since I switch quite frequently).
I bet it is. Thank goodness it's configurable at the OS level though (on MacOS and X at least). >> but, Creator is somehow not seeing the effects of that change in >> system-wide settings. I don't know enough about MacOS yet to know >> where that mapping ought to take place, though. "moveToEndOfLine" >> sounds like a higher-level event to me; but if Qt apps can only handle >> actual keys, how can it be fixed? > > Qt has the concept of "StandardKeys" > (http://qt.nokia.com/doc/4.5/qkeysequence.html#StandardKey-enum) > exactly for that reason. These are obviously hardcoded, though. > (look for QKeySequencePrivate::keyBindings[] in > http://qt.gitorious.org/qt/qt/blobs/master/src/gui/kernel/qkeysequence.cpp > if you are interested :) ) > So, this part is definitely a deficiency in Qt. Yep, I see it. So it would seem the fix is the Qt library, when it is loaded, should query the OS for those key bindings to replace the default hard-coded ones? Do you know the MacOS API to do that? _______________________________________________ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
