Talk:Retained mode

This article is extremely inaccurate, from

Retained Mode Graphics

One of the keys to understanding the role of the Visual object is to understand the difference between immediate mode and retained mode graphics systems. A standard Win32 application based on GDI or GDI+ uses an immediate mode graphics system. This means that the application is responsible for repainting the portion of the client area that is invalidated, due to an action such as a window being resized, or an object changing its visual appearance.

In contrast, WPF uses a retained mode system. This means application objects that have a visual appearance define a set of serialized drawing data. Once the drawing data is defined, the system is responsible thereafter for responding to all repaint requests for rendering the application objects. Even at run time, you can modify or create application objects, and still rely on the system for responding to paint requests. The power in a retained mode graphics system is that drawing information is always persisted in a serialized state by the application, but rendering responsibility left to the system. The following diagram shows how the application relies on WPF for responding to paint requests.

The article seems to imply that retained graphics has more to do with state in a retained mode renderer than it does with control. Actually, the need for state in a retained mode renderer is just a symptom of giving up control, and no state may be involved as long as the renderer can recompute what needs to be re-rendered.221.223.43.211 (talk) 05:02, 4 January 2010 (UTC)