1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rewrite AA_MacDontSwapCtrlAndMeta documentation

Browse Source 
Change-Id: Ifc41d0d341aed029e89baa3fc20f9535c1fb01d9
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
This commit is contained in:
Tor Arne Vestbø 2020-07-07 15:36:59 +02:00
parent 359616066e
commit 9ad1c6d835
1 changed files with 18 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
src/corelib/global/qnamespace.qdoc
View File

@ -139,13 +139,24 @@
set to true won't be used as a native menubar (e.g, the menubar at set to true won't be used as a native menubar (e.g, the menubar at
the top of the main screen on \macos). the top of the main screen on \macos).
\value AA_MacDontSwapCtrlAndMeta On \macos by default, Qt swaps the \value AA_MacDontSwapCtrlAndMeta Keyboard shortcuts on \macos are typically
Control and Meta (Command) keys (i.e., whenever Control is pressed, Qt based on the Command (or Cmd) keyboard modifier, represented by
sends Meta, and whenever Meta is pressed Control is sent). When this the ⌘ symbol. For example, the 'Copy' action is Command+C (⌘+C).
attribute is true, Qt will not do the flip. \l QKeySequence::StandardKey To ease cross platform development Qt will by default remap Command
will also flip accordingly (i.e., QKeySequence::Copy will be to the Qt::ControlModifier, to align with other platforms. This
Command+C on the keyboard regardless of the value set, though what is output for allows creating keyboard shortcuts such as "Ctrl+J", which on
QKeySequence::toString() will be different). \macos will then map to Command+J, as expected by \macos users. The
actual Control (or Ctrl) modifier on \macos, represented by ⌃, is
mapped to Qt::MetaModifier.
When this attribute is true Qt will not do the remapping, and pressing
the Command modifier will result in Qt::MetaModifier, while pressing
the Control modifier will result in Qt::ControlModifier.
Note that the \l QKeySequence::StandardKey sequences will always be
based on the same modifier (i.e., QKeySequence::Copy will be
Command+C regardless of the value set), but what is output for
QKeySequence::toString() will be different.
\value AA_Use96Dpi Assume the screen has a resolution of 96 DPI rather \value AA_Use96Dpi Assume the screen has a resolution of 96 DPI rather
than using the OS-provided resolution. This will cause font rendering than using the OS-provided resolution. This will cause font rendering