 | This article needs additional citations for verification. (September 2014) |
Retained mode in computer graphics is a major pattern of API design in graphics libraries,[1] in which
- the graphics library, instead of the client, retains the scene (complete object model of the rendering primitives) to be rendered and
- the client calls into the graphics library do not directly cause actual rendering, but make use of extensive indirection to resources, managed – thus retained – by the graphics library.[2] It does not preclude the use of double-buffering.[3]
Immediate mode is an alternative approach. Historically, retained mode has been the dominant style in GUI libraries;[4] however, both can coexist in the same library and are not necessarily exclusionary in practice.[5]
- ^ Jin, Zhefan (May 2006). "Retained-Mode Parallel Graphics Rendering for Cooperative Design Environments". 2006 10th International Conference on Computer Supported Cooperative Work in Design. pp. 1–6. doi:10.1109/CSCWD.2006.253142. ISBN 1-4244-0164-X. S2CID 5825966.
- ^ Quinn Radich (May 30, 2018). "Retained Mode Versus Immediate Mode". Win32 apps. Microsoft. Retrieved 21 December 2019.
- ^ stevewhims. "Predication queries - Win32 apps". learn.microsoft.com. Retrieved 2022-12-09.
- ^ Feldmeier, Alex (October 12, 2013). "GUI Programming". UWP Computer Science and Software Engineering Technical Report. Retrieved 22 December 2019.
Retained mode has been the standard for years. Just about every GUI is in retained mode.
- ^ QuinnRadich. "Retained Mode Versus Immediate Mode - Win32 apps". docs.microsoft.com. Retrieved 2020-08-21.