>     Also, the app is being fairly explicit IMO - if it does a
> MakeCurrent when another context is already current to another thread,
> then it's saying "I'm going multithreaded".

Its too late - one thread cannot safely update the other thread's dispatch
table to be thread-safe.

Reply via email to