Hi Steven,
osgViewer was never designed to be used in the way you want to use it,
there are almost certainly better ways of doing what you want to do
functionally and a simpler way that trying play games with who invokes
frame. It's just a bad approach so trying to help do something that
isn't
Thanks for the replies. This is mostly experimental and I have already been
calling frame() from a child thread for a while now without any problems as
long as I call createGraphicsContext() and realize() from the same child thread.
This effort is to streamline the initialization of the
Hi Steven,
What OS are you on? On OSX, event handling MUST happen from the main
thread, so you have to coordinate the frame loop between threads.
Ravi
On Tue, Sep 11, 2018 at 11:43 AM Robert Osfield
wrote:
> Hi Steven,
>
> I haven't heard of anyone trying to call frame from multiple threads
>
Hi Steven,
I haven't heard of anyone trying to call frame from multiple threads
before, and personally wouldn't recommend doing it. I have said why
you are wanting to do this so can't judge how sensible or daft it is.
If you want an application that has multiple threads that modifying
something
I am attempting to switch which thread I call viewer::frame in.
I realize my viewer in thread A, call viewer::frame() several times, do some
loading, then switch the call to viewer::frame() to thread B. When I do so the
items within the window still update but I am unable to move/resize/select
5 matches
Mail list logo
