AccessiblityĪlthough many users never use this, some users will only interact with your applications via assistive devices. 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 QWidget::setWindowIcon() on the main window in your application.
#Qt mac os x check for mac os x
Qt for Mac OS X is fully API compatible with Qt for Windows and X11, but Mac OS X is a significantly different platform to Windows and some special considerations must be made based on your audience. If your user base is small or mostly comes from the Windows or Unix worlds, these are minor issues much less important than trying to make a mass market product. The decisions that must be made to conform (widget sizes, widget layouts with respect to other widgets, window margins, placement of OK and Cancel, etc) must be made based on the user experience demanded by your application. This is the area where Qt is of least assistance. This is the most subjective, but there are many suggestions and guidelines in the Aqua style guidelines. Some "baggage" that Qt carries is in an effort to provide a widget on a platform for which an equivelant doesn't exist, or so that a single API can be used to do something, even if the API doesn't make entire sense for a specific widget. Of course Qt has other concerns to bear in mind, especially remaining cross-platform. This is a bit more subjective, but certainly Qt strives to provide the same feel as any Mac OS X application (and we consider situations where it doesn't achieve this to be bugs).
Qt's widgets use Appearance Manager on Mac OS X 10.2 and the new HIThemes on Mac OS X 10.3 and higher to implement the look, in other words we use Apple's own API's for doing the rendering. It is a huge topic, but the most important guidelines for GUI design are probably these:Īs with Cocoa/Carbon, Qt provides widgets that look like those described in the Human Interface Descriptions. This is a critical piece of Mac OS X (documentation can be found at ). (By doing this automatically, Qt makes it easier to port Qt applications to other platforms.) Aqua Qt handles this automatically, although it does not provide a means of interacting directly with the application menu. Mac 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, etc.
Qt does this via the QMenuBar abstraction. When an application is running as a first class citizen, it means that it can interact with specific components of the Mac OS X experience: The Global Menu Bar In fact, we use Carbon and HIView internally to communicate with OS X. Qt applications run as first class citizens, just like Cocoa, and Carbon applications. Normally when referring to a native Mac application, one really means an application that talks directly to the underlying window system, rather than one that uses some intermediary (for example Apple's X11 server, or a web browser). (See also the document Qt for Mac OS X - Specific Issues.) It shows the areas where Qt is compliant, and the grey areas where compliance is more questionable. This document explains what makes an application native on Mac OS X.
0 kommentar(er)
