diff options
Diffstat (limited to 'src/widgets/kernel/qwidgetaction.cpp')
| -rw-r--r-- | src/widgets/kernel/qwidgetaction.cpp | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/src/widgets/kernel/qwidgetaction.cpp b/src/widgets/kernel/qwidgetaction.cpp index 14369513da..c3fc6c7cfb 100644 --- a/src/widgets/kernel/qwidgetaction.cpp +++ b/src/widgets/kernel/qwidgetaction.cpp @@ -87,17 +87,17 @@ QT_BEGIN_NAMESPACE Note that it is up to the widget to activate the action, for example by reimplementing mouse event handlers and calling QAction::trigger(). - \bold {Mac OS X}: If you add a widget to a menu in the application's menu + \b {Mac OS X}: If you add a widget to a menu in the application's menu bar on Mac OS X, the widget will be added and it will function but with some limitations: \list 1 - \o The widget is reparented away from the QMenu to the native menu + \li The widget is reparented away from the QMenu to the native menu view. If you show the menu in some other place (e.g. as a popup menu), the widget will not be there. - \o Focus/Keyboard handling of the widget is not possible. - \o Due to Apple's design, mouse tracking on the widget currently does + \li Focus/Keyboard handling of the widget is not possible. + \li Due to Apple's design, mouse tracking on the widget currently does not work. - \o Connecting the triggered() signal to a slot that opens a modal + \li Connecting the triggered() signal to a slot that opens a modal dialog will cause a crash in Mac OS X 10.4 (known bug acknowledged by Apple), a workaround is to use a QueuedConnection instead of a DirectConnection. |