> =20 > > > It could be wrapped in something like USE_X11_THREADING as an=20 > > option. Anyway, in general the best description of things=20 > > and discussion I found was at=20 > > http://ask.slashdot.org/story/03/01/11/0043207/why-isnt-x11-th > > read-safe > > > And I'd caution that (in my experience) this is not specifically an X11 > issue, indeed the two times I tripped myself up with this were on WinXP > boxes, and a colleague here also tripped over this on WinXP-embedded. > > So WinXP doesn't do this robustly either (indeed, we found that it was > *very* sensitive to which graphics card and driver were used.) > I've done it for years with no issues. Windows is designed so that each thread creating a window gets its own messages (via a message loop). I think what most forget is a lot of the initializion done at the beginning of an app should actually be done per-thread (COM, etc.) oterhwise weird things happen (as well as messing with threading models). http://msdn.microsoft.com/en-us/library/windows/desktop/ms644928(v=vs.85).aspx
_______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
