nanogui: Changing properties from another thread
Subject:
Re: [nanogui] Changing properties from another thread
From:
"Greg Haerr" ####@####.####
Date:
28 Sep 2005 19:45:34 +0100
Message-Id: <08e501c5c45c$9e218780$0300a8c0@RDP>
: nxclient 7980: Wrong packet type 61 (expected 22)
These errors mean that the protocol on the connection between
the client(s) and server are out of sync. This typically happens
in a multithreaded app that is reading or writing the server
connection socket at the same time. In most cases, setting
up Nano-X THREADSAFE=Y will mutex block each GrXXX
api call until completion, but we've recently learned that
no thread can be in GrGetNextEvent waiting while other
threads are making GrXXX calls.
In other words, _every_ GrXXX api call, including the wait
for next event, must complete before _any_ other thread
makes a call. This can be accomplished by having only
one thread make GrXXX calls, and other threads passing
that information to the single calling thread. I don't know
the details behind FLTK, but it sounds like this process
isn't occuring.
Regards,
Greg
