[Openal-devel] Thread-local contexts

[Jason Daly]

Chris Robinson wrote:
>
> ctx2 would be current for that thread (assuming you mean alcMakeContextCurrent 
> for alcMakeCurrent). Both alcGetCurrentContext and alcGetThreadContext would 
> return it.
>   

Yes, alcMakeContextCurrent() is what I meant.  That seems a bit 
counter-intuitive to me.  Would it be better (after an 
alcMakeThreadCurrent() call) for an alcMakeContextCurrent() call to set 
the specified context current for both the global and the thread context?

I guess no, because the whole point of this is to kind of "override" the 
current context in your own thread while some background thread that 
probably wasn't written with this extension hums along on its merry way.

It just seems odd that alcMakeContextCurrent() might not make the 
specified context current in some cases.  I can't think of an 
alternative at the moment, though.


--"J"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://opensource.creative.com/pipermail/openal-devel/attachments/20090909/33e3f67d/attachment.html