The PySide.QtOpenGL.QGLWidget class is a widget for rendering OpenGL graphics.
PySide.QtOpenGL.QGLWidget provides functionality for displaying OpenGL graphics integrated into a Qt application. It is very simple to use. You inherit from it and use the subclass like any other PySide.QtGui.QWidget , except that you have the choice between using PySide.QtGui.QPainter and standard OpenGL rendering commands.
PySide.QtOpenGL.QGLWidget provides three convenient virtual functions that you can reimplement in your subclass to perform the typical OpenGL tasks:
- PySide.QtOpenGL.QGLWidget.paintGL() - Renders the OpenGL scene. Gets called whenever the widget needs to be updated.
- PySide.QtOpenGL.QGLWidget.resizeGL() - Sets up the OpenGL viewport, projection, etc. Gets called whenever the widget has been resized (and also when it is shown for the first time because all newly created widgets get a resize event automatically).
- PySide.QtOpenGL.QGLWidget.initializeGL() - Sets up the OpenGL rendering context, defines display lists, etc. Gets called once before the first time PySide.QtOpenGL.QGLWidget.resizeGL() or PySide.QtOpenGL.QGLWidget.paintGL() is called.
Here is a rough outline of how a PySide.QtOpenGL.QGLWidget subclass might look:
class MyGLDrawer(QGLWidget): def __init__(self, parent): QGLWidget.__init__(self, parent) pass def initializeGL(self): # Set up the rendering context, define display lists etc.: ... glClearColor(0.0, 0.0, 0.0, 0.0) glEnable(GL_DEPTH_TEST) ... def resizeGL(self, w, h): # setup viewport, projection etc.: glViewport(0, 0, w, h) ... glFrustum(...) ... def paintGL(self): # draw the scene: ... glRotatef(...) glMaterialfv(...) glBegin(GL_QUADS) glVertex3f(...) glVertex3f(...) ... glEnd() ...If you need to trigger a repaint from places other than PySide.QtOpenGL.QGLWidget.paintGL() (a typical example is when using timers to animate scenes), you should call the widget’s PySide.QtOpenGL.QGLWidget.updateGL() function.
Your widget’s OpenGL rendering context is made current when PySide.QtOpenGL.QGLWidget.paintGL() , PySide.QtOpenGL.QGLWidget.resizeGL() , or PySide.QtOpenGL.QGLWidget.initializeGL() is called. If you need to call the standard OpenGL API functions from other places (e.g. in your widget’s constructor or in your own paint functions), you must call PySide.QtOpenGL.QGLWidget.makeCurrent() first.
PySide.QtOpenGL.QGLWidget provides functions for requesting a new display format and you can also create widgets with customized rendering contexts .
You can also share OpenGL display lists between PySide.QtOpenGL.QGLWidget objects (see the documentation of the PySide.QtOpenGL.QGLWidget constructors for details).
Note that under Windows, the PySide.QtOpenGL.QGLContext belonging to a PySide.QtOpenGL.QGLWidget has to be recreated when the PySide.QtOpenGL.QGLWidget is reparented. This is necessary due to limitations on the Windows platform. This will most likely cause problems for users that have subclassed and installed their own PySide.QtOpenGL.QGLContext on a PySide.QtOpenGL.QGLWidget . It is possible to work around this issue by putting the PySide.QtOpenGL.QGLWidget inside a dummy widget and then reparenting the dummy widget, instead of the PySide.QtOpenGL.QGLWidget . This will side-step the issue altogether, and is what we recommend for users that need this kind of functionality.
On Mac OS X, when Qt is built with Cocoa support, a PySide.QtOpenGL.QGLWidget can’t have any sibling widgets placed ontop of itself. This is due to limitations in the Cocoa API and is not supported by Apple.
The PySide.QtOpenGL.QGLWidget creates a GL overlay context in addition to the normal context if overlays are supported by the underlying system.
If you want to use overlays, you specify it in the format . (Note: Overlay must be requested in the format passed to the PySide.QtOpenGL.QGLWidget constructor.) Your GL widget should also implement some or all of these virtual methods:
- PySide.QtOpenGL.QGLWidget.paintOverlayGL()
- PySide.QtOpenGL.QGLWidget.resizeOverlayGL()
- PySide.QtOpenGL.QGLWidget.initializeOverlayGL()
These methods work in the same way as the normal PySide.QtOpenGL.QGLWidget.paintGL() etc. functions, except that they will be called when the overlay context is made current. You can explicitly make the overlay context current by using PySide.QtOpenGL.QGLWidget.makeOverlayCurrent() , and you can access the overlay context directly (e.g. to ask for its transparent color) by calling PySide.QtOpenGL.QGLWidget.overlayContext() .
On X servers in which the default visual is in an overlay plane, non-GL Qt windows can also be used for overlays.
As described above, subclass PySide.QtOpenGL.QGLWidget to render pure 3D content in the following way:
- Reimplement the QGLWidget.initializeGL() and QGLWidget.resizeGL() to set up the OpenGL state and provide a perspective transformation.
- Reimplement QGLWidget.paintGL() to paint the 3D scene, calling only OpenGL functions to draw on the widget.
It is also possible to draw 2D graphics onto a PySide.QtOpenGL.QGLWidget subclass, it is necessary to reimplement QGLWidget.paintEvent() and do the following:
- Construct a PySide.QtGui.QPainter object.
- Initialize it for use on the widget with the QPainter.begin() function.
- Draw primitives using PySide.QtGui.QPainter ‘s member functions.
- Call QPainter.end() to finish painting.
Overpainting 2D content on top of 3D content takes a little more effort. One approach to doing this is shown in the Overpainting example.
As of Qt version 4.8, support for doing threaded GL rendering has been improved. There are three scenarios that we currently support:
- Buffer swapping in a thread.
Swapping buffers in a double buffered context may be a synchronous, locking call that may be a costly operation in some GL implementations. Especially so on embedded devices. It’s not optimal to have the CPU idling while the GPU is doing a buffer swap. In those cases it is possible to do the rendering in the main thread and do the actual buffer swap in a separate thread. This can be done with the following steps:
- Call PySide.QtOpenGL.QGLWidget.doneCurrent() in the main thread when the rendering is finished.
- Notify the swapping thread that it can grab the context.
- Make the rendering context current in the swapping thread with PySide.QtOpenGL.QGLWidget.makeCurrent() and then call PySide.QtOpenGL.QGLWidget.swapBuffers() .
- Call PySide.QtOpenGL.QGLWidget.doneCurrent() in the swapping thread and notify the main thread that swapping is done.
Doing this will free up the main thread so that it can continue with, for example, handling UI events or network requests. Even if there is a context swap involved, it may be preferable compared to having the main thread wait while the GPU finishes the swap operation. Note that this is highly implementation dependent.
- Texture uploading in a thread.
Doing texture uploads in a thread may be very useful for applications handling large amounts of images that needs to be displayed, like for instance a photo gallery application. This is supported in Qt through the existing PySide.QtOpenGL.QGLWidget.bindTexture() API. A simple way of doing this is to create two sharing QGLWidgets. One is made current in the main GUI thread, while the other is made current in the texture upload thread. The widget in the uploading thread is never shown, it is only used for sharing textures with the main thread. For each texture that is bound via PySide.QtOpenGL.QGLWidget.bindTexture() , notify the main thread so that it can start using the texture.
- Using PySide.QtGui.QPainter to draw into a PySide.QtOpenGL.QGLWidget in a thread.
In Qt 4.8, it is possible to draw into a PySide.QtOpenGL.QGLWidget using a PySide.QtGui.QPainter in a separate thread. Note that this is also possible for QGLPixelBuffers and QGLFramebufferObjects. Since this is only supported in the GL 2 paint engine, OpenGL 2.0 or OpenGL ES 2.0 is required.
QGLWidgets can only be created in the main GUI thread. This means a call to PySide.QtOpenGL.QGLWidget.doneCurrent() is necessary to release the GL context from the main thread, before the widget can be drawn into by another thread. Also, the main GUI thread will dispatch resize and paint events to a PySide.QtOpenGL.QGLWidget when the widget is resized, or parts of it becomes exposed or needs redrawing. It is therefore necessary to handle those events because the default implementations inside PySide.QtOpenGL.QGLWidget will try to make the PySide.QtOpenGL.QGLWidget ‘s context current, which again will interfere with any threads rendering into the widget. Reimplement QGLWidget.paintEvent() and QGLWidget.resizeEvent() to notify the rendering thread that a resize or update is necessary, and be careful not to call the base class implementation. If you are rendering an animation, it might not be necessary to handle the paint event at all since the rendering thread is doing regular updates. Then it would be enough to reimplement QGLWidget.paintEvent() to do nothing.
As a general rule when doing threaded rendering: be aware that binding and releasing contexts in different threads have to be synchronized by the user. A GL rendering context can only be current in one thread at any time. If you try to open a PySide.QtGui.QPainter on a PySide.QtOpenGL.QGLWidget and the widget’s rendering context is current in another thread, it will fail.
Note that under X11 it is necessary to set the Qt.AA_X11InitThreads application attribute to make the X11 library and GLX calls thread safe, otherwise the above scenarios will fail.
In addition to this, rendering using raw GL calls in a separate thread is supported.
OpenGL is a trademark of Silicon Graphics, Inc. in the United States and other countries.
See also
PySide.QtOpenGL.QGLPixelBuffer Hello GL Example 2D Painting Example Overpainting Example Grabber Example
Parameters: |
|
---|
Return type: | PySide.QtCore.bool |
---|
Returns true if the widget is doing automatic GL buffer swapping; otherwise returns false.
Parameters: |
|
---|---|
Return type: | PySide.QtOpenGL.GLuint |
Parameters: |
|
---|---|
Return type: | PySide.QtOpenGL.GLuint |
Calls QGLContext:::bindTexture(pixmap , target , format ) on the currently set context.
Parameters: | fileName – unicode |
---|---|
Return type: | PySide.QtOpenGL.GLuint |
This is an overloaded function.
Calls QGLContext::bindTexture(fileName ) on the currently set context.
Parameters: |
|
---|---|
Return type: | PySide.QtOpenGL.GLuint |
Parameters: |
|
---|---|
Return type: | PySide.QtOpenGL.GLuint |
Calls QGLContext:::bindTexture(image , target , format ) on the currently set context.
Return type: | PySide.QtOpenGL.QGLColormap |
---|
Returns the colormap for this widget.
Usually it is only top-level widgets that can have different colormaps installed. Asking for the colormap of a child widget will return the colormap for the child’s top-level widget.
If no colormap has been set for this widget, the PySide.QtOpenGL.QGLColormap returned will be empty.
Return type: | PySide.QtOpenGL.QGLContext |
---|
Returns the context of this widget.
It is possible that the context is not valid (see PySide.QtOpenGL.QGLWidget.isValid() ), for example, if the underlying hardware does not support the format attributes that were requested.
Parameters: | img – PySide.QtGui.QImage |
---|---|
Return type: | PySide.QtGui.QImage |
Converts the image img into the unnamed format expected by OpenGL functions such as glTexImage2D(). The returned image is not usable as a PySide.QtGui.QImage , but QImage.width() , QImage.height() and QImage.bits() may be used with OpenGL. The GL format used is GL_RGBA .
Parameters: | tx_id – PySide.QtOpenGL.GLuint |
---|
Calls QGLContext::deleteTexture(id ) on the currently set context.
Makes no GL context the current context. Normally, you do not need to call this function; PySide.QtOpenGL.QGLContext calls it as necessary. However, it may be useful in multithreaded environments.
Return type: | PySide.QtCore.bool |
---|
Returns true if the contained GL rendering context has double buffering; otherwise returns false.
See also
Parameters: |
|
---|
Calls the corresponding QGLContext.drawTexture() with target , textureId , and textureTarget for this widget’s context.
Parameters: |
|
---|
Calls the corresponding QGLContext.drawTexture() with point , textureId , and textureTarget for this widget’s context.
Return type: | PySide.QtOpenGL.QGLFormat |
---|
Returns the format of the contained GL rendering context.
See also
PySide.QtOpenGL.QGLWidget.setFormat()
Executes the virtual function PySide.QtOpenGL.QGLWidget.paintGL() .
The widget’s rendering context will become the current context and PySide.QtOpenGL.QGLWidget.initializeGL() will be called if it hasn’t already been called.
Initializes OpenGL for this widget’s context. Calls the virtual function PySide.QtOpenGL.QGLWidget.initializeGL() .
Parameters: | withAlpha – PySide.QtCore.bool |
---|---|
Return type: | PySide.QtGui.QImage |
Returns an image of the frame buffer. If withAlpha is true the alpha channel is included.
Depending on your hardware, you can explicitly select which color buffer to grab with a glReadBuffer() call before calling this function.
This virtual function is called once before the first call to PySide.QtOpenGL.QGLWidget.paintGL() or PySide.QtOpenGL.QGLWidget.resizeGL() , and then once whenever the widget has been assigned a new PySide.QtOpenGL.QGLContext . Reimplement it in a subclass.
This function should set up any required OpenGL context rendering flags, defining display lists, etc.
There is no need to call PySide.QtOpenGL.QGLWidget.makeCurrent() because this has already been done when this function is called.
This virtual function is used in the same manner as PySide.QtOpenGL.QGLWidget.initializeGL() except that it operates on the widget’s overlay context instead of the widget’s main context. This means that PySide.QtOpenGL.QGLWidget.initializeOverlayGL() is called once before the first call to PySide.QtOpenGL.QGLWidget.paintOverlayGL() or PySide.QtOpenGL.QGLWidget.resizeOverlayGL() . Reimplement it in a subclass.
This function should set up any required OpenGL context rendering flags, defining display lists, etc. for the overlay context.
There is no need to call PySide.QtOpenGL.QGLWidget.makeOverlayCurrent() because this has already been done when this function is called.
Return type: | PySide.QtCore.bool |
---|
Returns true if this widget’s GL context is shared with another GL context, otherwise false is returned. Context sharing might not be possible if the widgets use different formats.
See also
Return type: | PySide.QtCore.bool |
---|
Returns true if the widget has a valid GL rendering context; otherwise returns false. A widget will be invalid if the system has no OpenGL support .
Makes this widget the current widget for OpenGL operations, i.e. makes the widget’s rendering context the current OpenGL rendering context.
Makes the overlay context of this widget current. Use this if you need to issue OpenGL commands to the overlay context outside of PySide.QtOpenGL.QGLWidget.initializeOverlayGL() , PySide.QtOpenGL.QGLWidget.resizeOverlayGL() , and PySide.QtOpenGL.QGLWidget.paintOverlayGL() .
Does nothing if this widget has no overlay.
Return type: | PySide.QtOpenGL.QGLContext |
---|
Returns the overlay context of this widget, or 0 if this widget has no overlay.
See also
This virtual function is called whenever the widget needs to be painted. Reimplement it in a subclass.
There is no need to call PySide.QtOpenGL.QGLWidget.makeCurrent() because this has already been done when this function is called.
This virtual function is used in the same manner as PySide.QtOpenGL.QGLWidget.paintGL() except that it operates on the widget’s overlay context instead of the widget’s main context. This means that PySide.QtOpenGL.QGLWidget.paintOverlayGL() is called whenever the widget’s overlay needs to be painted. Reimplement it in a subclass.
There is no need to call PySide.QtOpenGL.QGLWidget.makeOverlayCurrent() because this has already been done when this function is called.
Parameters: | c – PySide.QtGui.QColor |
---|
Convenience function for specifying the clearing color to OpenGL. Calls glClearColor (in RGBA mode) or glClearIndex (in color-index mode) with the color c . Applies to this widgets GL context.
Parameters: | c – PySide.QtGui.QColor |
---|
Convenience function for specifying a drawing color to OpenGL. Calls glColor4 (in RGBA mode) or glIndex (in color-index mode) with the color c . Applies to this widgets GL context.
Note
This function is not supported on OpenGL/ES 2.0 systems.
Parameters: |
|
---|---|
Return type: |
Renders the current scene on a pixmap and returns the pixmap.
You can use this method on both visible and invisible PySide.QtOpenGL.QGLWidget objects.
This method will create a pixmap and a temporary PySide.QtOpenGL.QGLContext to render on the pixmap. It will then call PySide.QtOpenGL.QGLWidget.initializeGL() , PySide.QtOpenGL.QGLWidget.resizeGL() , and PySide.QtOpenGL.QGLWidget.paintGL() on this context. Finally, the widget’s original GL context is restored.
The size of the pixmap will be w pixels wide and h pixels high unless one of these parameters is 0 (the default), in which case the pixmap will have the same size as the widget.
If useContext is true, this method will try to be more efficient by using the existing GL context to render the pixmap. The default is false. Only use true if you understand the risks. Note that under Windows a temporary context has to be created and usage of the useContext parameter is not supported.
Overlays are not rendered onto the pixmap.
If the GL rendering context and the desktop have different bit depths, the result will most likely look surprising.
Note that the creation of display lists, modifications of the view frustum etc. should be done from within PySide.QtOpenGL.QGLWidget.initializeGL() . If this is not done, the temporary PySide.QtOpenGL.QGLContext will not be initialized properly, and the rendered pixmap may be incomplete/corrupted.
Parameters: |
|
---|
Renders the string str into the GL context of this widget.
x and y are specified in window coordinates, with the origin in the upper left-hand corner of the window. If font is not specified, the currently set application font will be used to render the string. To change the color of the rendered text you can use the glColor() call (or the PySide.QtOpenGL.QGLWidget.qglColor() convenience function), just before the PySide.QtOpenGL.QGLWidget.renderText() call.
The listBase parameter is obsolete and will be removed in a future version of Qt.
Note
This function clears the stencil buffer.
Note
This function is not supported on OpenGL/ES systems.
Note
This function temporarily disables depth-testing when the text is drawn.
Note
This function can only be used inside a QPainter.beginNativePainting() / QPainter.endNativePainting() block if the default OpenGL paint engine is QPaintEngine.OpenGL . To make QPaintEngine.OpenGL the default GL engine, call QGL::setPreferredPaintEngine( QPaintEngine.OpenGL ) before the PySide.QtGui.QApplication constructor.
Overpaint with QPainter.drawText() instead.
Parameters: |
|
---|
This is an overloaded function.
x , y and z are specified in scene or object coordinates relative to the currently set projection and model matrices. This can be useful if you want to annotate models with text labels and have the labels move with the model as it is rotated etc.
Note
This function is not supported on OpenGL/ES systems.
Note
If depth testing is enabled before this function is called, then the drawn text will be depth-tested against the models that have already been drawn in the scene. Use glDisable(GL_DEPTH_TEST) before calling this function to annotate the models without depth-testing the text.
Overpaint with QPainter.drawText() instead.
Parameters: |
|
---|
This virtual function is called whenever the widget has been resized. The new size is passed in width and height . Reimplement it in a subclass.
There is no need to call PySide.QtOpenGL.QGLWidget.makeCurrent() because this has already been done when this function is called.
Parameters: |
|
---|
This virtual function is used in the same manner as PySide.QtOpenGL.QGLWidget.paintGL() except that it operates on the widget’s overlay context instead of the widget’s main context. This means that PySide.QtOpenGL.QGLWidget.resizeOverlayGL() is called whenever the widget has been resized. The new size is passed in width and height . Reimplement it in a subclass.
There is no need to call PySide.QtOpenGL.QGLWidget.makeOverlayCurrent() because this has already been done when this function is called.
Parameters: | on – PySide.QtCore.bool |
---|
If on is true automatic GL buffer swapping is switched on; otherwise it is switched off.
If on is true and the widget is using a double-buffered format, the background and foreground GL buffers will automatically be swapped after each PySide.QtOpenGL.QGLWidget.paintGL() call.
The buffer auto-swapping is on by default.
Parameters: | map – PySide.QtOpenGL.QGLColormap |
---|
Set the colormap for this widget to cmap . Usually it is only top-level widgets that can have colormaps installed.
See also
Swaps the screen contents with an off-screen buffer. This only works if the widget’s format specifies double buffer mode.
Normally, there is no need to explicitly call this function because it is done automatically after each widget repaint, i.e. each time after PySide.QtOpenGL.QGLWidget.paintGL() has been executed.
Updates the widget by calling PySide.QtOpenGL.QGLWidget.glDraw() .
Updates the widget’s overlay (if any). Will cause the virtual function PySide.QtOpenGL.QGLWidget.paintOverlayGL() to be executed.
The widget’s rendering context will become the current context and PySide.QtOpenGL.QGLWidget.initializeGL() will be called if it hasn’t already been called.