I'm assuming that it is legal to call Glide2's grSstQueryHardware before calling grSstWinOpen, because the SDK states it.
But what about Glide3? When is grGetString(GR_EXTENSIONS) expected to return the proper extension string? Right after grGlideInit, or only after grSstWinOpen?
What about grGet()?
(specifically for GR_NUM_TMU, but a general answer would be cool)
I'm asking because my wrapper does not return a proper extension string until grSstWinOpen has been called, and for Gonetz's Glide64 it actually gets away with it. But I'm very unsure whether or not this is correct behaviour, and if it will work with other Glide3 stuff.
If it is correct behaviour to return errors or bogus from queries up to that point, I would very much like to extend this behaviour to all Glide3 queries.
But what about Glide3? When is grGetString(GR_EXTENSIONS) expected to return the proper extension string? Right after grGlideInit, or only after grSstWinOpen?
What about grGet()?
(specifically for GR_NUM_TMU, but a general answer would be cool)
I'm asking because my wrapper does not return a proper extension string until grSstWinOpen has been called, and for Gonetz's Glide64 it actually gets away with it. But I'm very unsure whether or not this is correct behaviour, and if it will work with other Glide3 stuff.
If it is correct behaviour to return errors or bogus from queries up to that point, I would very much like to extend this behaviour to all Glide3 queries.