<br><div class="gmail_quote">On 5 April 2011 04:46, Brian Paul <span dir="ltr"><<a href="mailto:brianp@vmware.com">brianp@vmware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
What kind of state are you interested in? Something beyond the usual glGet*() queries?<font color="#888888"><br>
</font></blockquote></div><br>Hey,<br><br>Part of my interest is in knowing how much one can/can't do with Mesa and OpenGL. Being new to Mesa, and relatively so to OpenGL as well I welcome any corrections or advice on what I say below.<br>
<br>I am interested in stuff beyond the glGet* queires. In regards to the glGet* queries these would require modification of the code running above Mesa, right? Is there a way to tap directly into the state these queries are addressing, or does that amount to the same thing?<br>
<br>With regards to other functionality I'm thinking of stuff along the lines of can one get information on and interact with the command buffer? Can one directly access buffers such as the depth buffer or the front buffer (though if I understand correctly one can also read this back using glReadPixels). Can one inspect shaders using the software renderer to a greater degree than with hardware? For example, being able to check values of variables during shader execution?<br>
<br>Kind regards,<br><br><br>Bryce Van Dyk.<br>