The setWindowIcon() call can be made as often as necessary, providing an icon that can be easily updated. The icon can be set by calling QWindow::setWindowIcon() from the main window in your application. To provide the expected behavior for Qt applications on macOS, the Qt::Key_Meta, Qt::MetaModifier, and Qt::META enum values correspond to the Control keys on the standard Apple keyboard, and the Qt::Key_Control, Qt::ControlModifier, and Qt::CTRL enum values correspond to the Command keys. At this time there are no MenuRole identifiers for them, but they will be auto-detected just like the application menu items when the QAction has the default TextHeuristicRole. It's important that you create these menu items with the standard shortcuts so that the corresponding editing features will be enabled in the dialogs. Other standard menu items such as Cut, Copy, Paste and Select All are applicable both in your application and in some native dialogs such as QFileDialog. Qt handles these conventions, although it does not provide a means of interacting directly with the application menu.Д®ach QAction has a menuRole property which controls the special placement of application menu items however by default the menuRole is TextHeuristicRole which mean the menu items will be auto-detected by their text. macOS users expect to have a menu bar at the top of the screen and Qt honors this.ДЄdditionally, users expect certain conventions to be respected, for example the application menu should contain About, Preferences, Quit, and so on. Qt provides support for the Global Menu Bar with QMenuBar. The section with the list of limitations below has more information. Using native menu bars introduces certain limitations on Qt classes. The first one created will be designated the default menu bar and will be used whenever a default menu bar is needed. However, you can create a different default menu bar by creating a parentless QMenuBar. The default menu bar on Qt is an empty menu bar. If all else fails, a default menu bar will be created. These tests are followed all the way up the parent window chain until one of the above rules is satisfied.

If the window has no parent, then the default menu bar is used (as documented below).

If no menu bar is specified, then a default menu bar is used (as documented below).

If the window is modal, then its menu bar is used.

If the window has a QMenuBar, then it is used.

However, if you have special needs, the Qt implementation currently selects a menu bar by starting at the active window (for example, QGuiApplication::focusWindow()) and applying the following tests: Fitting this into existing Qt applications is normally automatic. Qt detects menu bars and turns them into Mac native menu bars. This is the most common use of right mouse clicks, and maps to a control-click with the macOS one-button mouse support. This will map to a context menu event, for example, a menu that will display a pop-up selection. The QContextMenuEvent class provides right mouse click support for macOS applications. Also it is impossible to paint outside of a paint event so Qt::WA_PaintOutsidePaintEvent has no effect either. MacOS always double buffers the screen, therefore, the Qt::WA_PaintOnScreen attribute has no effect.

QMainWindow::unifiedTitleAndToolBarOnMac.

The following lists a set of useful attributes that can be used to tweak applications on macOS: The Qt Widget Gallery page contains sample images of applications using the macOS platform theme. Note that although Qt's widgets use AppKit under the hood for look and feel, it does not represent each individual Qt Widget as a wrapped native control. As with Cocoa, Qt provides widgets that look like those described in the macOS Human Interface Guidelines. The Aqua style is an essential part of the macOS platform. macOS terminologies and specific processes are found at. This page outlines the main issues regarding macOS support in Qt.

Qt mac os version