Lines Matching refs:To
37 In many situations, applications want to detect characteristics of a
50 may want to pick one over the other. One such situation is when the
53 hardware implementation is blacklisted due to known bugs.
55 This extension provides a mechanism for the application to query all of
57 addition, this extension provides a mechanism for applications to create
58 contexts with respect to a specific renderer.
95 Additions to the OpenGL / WGL Specifications
99 Additions to the GLX 1.4 Specification
101 [Add to Section 3.3.2 "GLX Versioning" of the GLX Specification]
103 To obtain information about the available renderers for a particular
124 memory available to the renderer
134 value is suitable to be supplied
137 attribute to
215 UNRESOLVED. The common case for desktop renderers is to prefer
240 for software implementations, so it seems reasonable for this to be
247 8) What happens if a fbconfig is used to create context on a renderer
254 9) In addition to being able to query the supported versions, should
255 applications also be able to query the supported extensions?
261 benefit to applications.
292 UNRESOLVED. Based on ISV feedback, this is important information to
293 provide to the application. Given the variety of possible hardware
298 It is likely that this will be left to a layered extension.
300 12) Should capability queries similar to those in
309 this extension it is a bit of a pain for a portable application to query
317 RESOLVED. It is fairly compelling for the post-creation queries to
323 15) Should the string queries be required to return the same values as
342 should make every attempt to return as much information as is
353 Change wording of issue #8 to be more
355 Make some wording changes to issue #10 to
369 Version 6, 2013/10/25 - Fix a typo. Update the list of functions to
385 of the GLX spec to modify.
Indexes created Tue Aug 04 00:24:20 UTC 2026