The child process fixes have not been committed to LyX 1.3.6cvs yet. I still have to apply a subset of your "win32_10jan05.diff" patch
Indeed. And having applied this subset, you find that LyX blocks until your
graphics images are converted and loaded onto the screen, no?
Who cares? If we don't tell the Windows users that LyX does not block on Linux, they will be very happy with the current status.
BTW: What are your plans for the remaining fixes, in particular for the 1.3.6 branch? Do you intend to do a major code redesign or will you just submit a small patch with the known limitations (I have no objections against the second alternative)?
I plan one more fix only really which is to address the blocking thing in as simple a manner as possible. That's conceptually little more than
s/spawnvp/CreateProcess/
in forkedcall.C and
s/waitpid/WaitForSingleObject/
in forkedcall.C and forkedcontr.C
There's a little housekeeping associated with storing a HANDLE rather than a pid_t, but not much.
The code in ispell.C, lyxserver.C will remain disabled in LyX 1.3.x.
Angus
