By Michal_IT5
on Wed, 06/20/2012 - 17:08
Hi
First off, very nice work with the framework!
We have an AR Application, which we'd love to use the tracking part of your library with. However, both of those libraries use their own OpenGL context, and working around this limitation by ignoring your Rendering Module and using your UpdateCallback instead gives me a headache. The reason for this are the multithreading issues in conjuncture with our engine, as I upload the camera texture manually.
It would be great if your framework was less restrictive/could be called in a passive manner without it's own rendering loop.
Please give me an update on this matter if you're planning to consider this, or feel free to tell me an alternative workaround.
With best regards,
Michal Domanski, IT5
Re: QCAR Feature Request : OpenGL Context
Re: QCAR Feature Request : OpenGL Context
Re: QCAR Feature Request : OpenGL Context
Re: QCAR Feature Request : OpenGL Context
Re: QCAR Feature Request : OpenGL Context
Re: QCAR Feature Request : OpenGL Context
Re: QCAR Feature Request : OpenGL Context
Re: QCAR Feature Request : OpenGL Context
Re: QCAR Feature Request : OpenGL Context
Re: QCAR Feature Request : OpenGL Context
Re: QCAR Feature Request : OpenGL Context