Version 2.2 Features
Input objects
The input object is used to handle the events (such as press, release, move, etc) from an input device (mouse or similar). The type of events handled by the input object can be customised, i.e the user can decide which events will be supported by supplying the customised user code for handling the events. The runtime will process hit detection for pointer events and return the object(s), if any, that has an active area that intersects with the position at which the pointer event occurred.
Texture fonts
The texture fonts feature refers to using OpenGL textures to draw raster (bitmap) text. Using textures as opposed to drawing with gIBitmap provides more functionality, such as rotation and some scaling. It also greatly reduces bus traffic, as the textures are already loaded into the graphics accelerator memory.
Display lists
Drawing graphics using display lists is supported in QCG. If a graphical object is flagged as being a display list, specific drawing commands will be code generated. This will result in constructing and drawing a display list that contains all graphics within the graphical object. Fonts and circles can be optionally drawn with display lists.
Frame VPL sorting algorithm
The Frame VPL (visual priority level) sorting algorithm has been updated and now uses a more optimal sorting algorithm that will significantly improve both initialization used and runtime performance.
GDI driver lookup optimization
Previously, the GDI driver function for each GDI object was looked up at each call to a GDI object driver function. In 2.2, the driver for each object is only looked up at initialization time and is then cached for use on each call. This can save significant CPU cycles.
