On 12 March 2013 17:46, Ian Romanick <i...@freedesktop.org> wrote: > Right... the extension also adds an attribute that can only be used with > glXCreateContextAttribsARB. > Yeah, all I was saying is that it probably wouldn't be too hard to word things along the lines of "If glXCreateContextAttribsARB() isn't available GLX_RENDERER_ID_MESA goes away, and only one renderer is available / visible.". Perhaps it's not worth it though.
> My thinking was that it will be very rare for multiple renderers to support > the same GL versions and different extension strings... at least in a way > that would cause apps to make different context creation decisions. > I guess that makes sense in the very coarse "I need at least GL3" way. > Part of the thinking is that it would force regularity in how the version is > advertised. Otherwise everyone will have a different kind of string, and > the currently annoying situation of parsing implementation dependent strings > continues. > > Maybe GLX_RENDERER_VERSION_MESA should also be allowed with > glXQueryRendererStringMESA? > Yeah, I think that makes sense. > I also based this on ISV feedback. Some just wanted to know what the > hardware was, and others wanted to know that and who made the driver. I was > really trying to get away from "just parse this random string" for as much > of the API as possible. It seems like this should only make things easier > for apps... should. > In theory you could add a GL vendor ID similar to the PCI vendor ID, but then you'd have to allocate those globally, which would probably be annoying. So, yeah. _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
