stefandoesinger at gmx.at
Thu Apr 6 03:23:11 CDT 2006
> The wineserver would have to trigger some code in the client, either by
> having a signal or a generic background thread that could do it on behalf
> of the other process.
> Such a scheme has been discussed before for things like CreateRemoteThread
> and friends.
That would be usefull too for multithreaded direct3d. Somehow we have to bring
another thread to releasing the glxContext, so we can re-use it in a new
Any chance we can do this with signals? e.g. SIGUSER1 to call a wine-provided
callback function, which calls callbacks registered by the various dlls?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 191 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20060406/c6d7eb0b/attachment.pgp
More information about the wine-devel