Lines Matching refs:latched
148 libraries to avoid disturbing selector and latched state. The
168 We call OpenGL state "latched" if the state is set by one OpenGL
172 are latched by vertex array specification commands to determine
177 The existence of selectors and latched state in the OpenGL API
181 state selectors and latched state. In many cases, selectors and
182 latched state were introduced by extensions as OpenGL evolved to
209 The OpenGL API has latched state for vertex array buffer objects
229 the current array buffer state is latched as the binding for the
245 Selectors and latched state create problems for layered libraries
247 modified to update some other state and latched state means implicit
257 evolves or its usage varies. For latched state, layered libraries
259 because latched pixel store state is not what the library expects.
260 Querying or pushing the latched state, setting the latched state
261 explicitly, performing the operation involving latched state, and
262 then restoring or popping the latched state avoids entanglements
263 with latched state but at considerable cost.
335 selector or latched state as follows:
349 selector or latched state (assuming the client attrib state does
3268 (5) The OpenGL API has "latched" state. Explain latched state
3269 and how this extension addresses latched state.
3271 RESOLVED: Examples of latched state in the OpenGL API are the
3287 state variable is to be updated or queried, latched state is
3296 Fixing the latched state problem with additional API is involved
3302 This extension addresses latched state by adding a new command
3309 latched client state so layered libraries that want well-defined
3310 latched client state can use these commands.
4064 object selector (vaobj) and the latched buffer state (buffer).
4067 selector-free. The latched buffer is an explicit parameter to
4071 works to avoid disturbing latched client vertex array buffer