|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
I tought that glScissor was some kind of state which was not affected by some other graphic states, but I found the following behaviour :
If I change the projection matrix (GL_PROJECTION, glLoadIdentity, glOrtho, glTranslatef) and don't call glScissor then it looks as if the scissor box (GL_SCISSOR_BOX) was reset to the whole window.
In the case where the scissor is not explicitely changed and the projection matrix was changed, I run into the situation where calling glGetIntegerv before glScissor returns the right box, however if I don't call glScissor (while setting the exact same values...) the subsequent drawing command don't get properly scissored.
I've only tested on a Radeon HD 2600, so this might not be a problem of that card (or others) but more likely a misinterpretation of myself on how glScissor should work.
I this is a misinterpretation, should I force glScissor (with the same values) in some other state changes ?
(for now my strategy was to only emit glScissor calls when the actual scissor box changed. Now I will also emit this call when a projection matrix change occured, but I want to know if I should take some other states into account)
Thanks for any information on this problem,
Raphael _______________________________________________ Do not post admin requests to the list. They will be ignored. Mac-opengl mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.