Adding an Accelerated Graphics Driver in Qtopia CoreIn Qtopia Core, painting is a pure software implementation and is normally performed in two steps: Each window is rendered onto a QWSWindowSurface using QPaintEngine, and then the server composes the surface images and copies them to the screen (see the Qtopia Core Architecture documentation for details). Qtopia Core uses QRasterPaintEngine (a raster-based implementation of QPaintEngine) to implement painting operations and QScreen to implement window composition. Starting with Qtopia Core 4.2, it is possible to add an accelerated graphics driver to take advantage of available hardware resources, using the following approach:
Warning: This feature is under development and is subject to change. Step 1: Create a Custom ScreenCreate a custom screen by deriving from the QScreen class. The connect(), disconnect(), initDevice() and shutdownDevice() functions are declared as pure virtual functions in QScreen and must be implemented. These functions are used to configure the hardware, or query its configuration. The connect() and disconnect() are called by both the server and client processes, while the initDevice() and shutdownDevice() functions are only called by the server process. You might want to accelerate the final copying to the screen by reimplementing the blit() and solidFill() functions. Step 2: Implement a Custom Raster Paint EngineImplement the painting operations by subclassing the QRasterPaintEngine class. To accelerate a graphics primitive, simply reimplement the corresponding function in your custom paint engine. If there is functionality you do not want to reimplement (such as certain pens, brushes, modes, etc.), you can just call the corresponding base class implementation. Step 3: Make the Paint Device Aware of Your Paint EngineTo activate your paint engine you must create a subclass of the QCustomRasterPaintDevice class and reimplement its paintEngine() function. Let this function return a pointer to your paint engine. In addition, the QCustomRasterPaintDevice::memory() function must be reimplemented to return a pointer to the buffer where the painting should be done.
Step 4: Make the Window Surface Aware of Your Paint DeviceDerive from the QWSWindowSurface class and reimplement its paintDevice() function. Make this function return a pointer to your custom raster paint device. Step 5: Enable the Screen to Create an Instance of Your Window SurfaceFinally, reimplement QScreen's createSurface() function and make this function able to create an instance of your QWSWindowSurface subclass. |
Publicité
Best OfActualités les plus luesSemaine
Mois
Année
Le Qt Developer Network au hasardComment fermer une applicationLe Qt Developer Network est un réseau de développeurs Qt anglophone, où ils peuvent partager leur expérience sur le framework. Lire l'article.
CommunautéRessources
Liens utilesContact
Qt dans le magazine |
Cette page est une traduction d'une page de la documentation de Qt, écrite par Nokia Corporation and/or its subsidiary(-ies). Les éventuels problèmes résultant d'une mauvaise traduction ne sont pas imputables à Nokia. | Qt 4.2 | |
Copyright © 2012 Developpez LLC. Tous droits réservés Developpez LLC. Aucune reproduction, même partielle, ne peut être faite de ce site et de l'ensemble de son contenu : textes, documents et images sans l'autorisation expresse de Developpez LLC. Sinon, vous encourez selon la loi jusqu'à 3 ans de prison et jusqu'à 300 000 E de dommages et intérêts. Cette page est déposée à la SACD. | ||
Vous avez déniché une erreur ? Un bug ? Une redirection cassée ? Ou tout autre problème, quel qu'il soit ? Ou bien vous désirez participer à ce projet de traduction ? N'hésitez pas à nous contacter ou par MP ! |
Copyright © 2000-2012 - www.developpez.com