M
Michael
I have an app with an FXRuby UI that does some fairly heavy data
processing. I've implemented an extension to put the processing into
C, so all is right the world there.
The issue is that I'm attempting to kick off the processing in a
separate thread to keep the UI responsive to the user, and it isn't
working. I was under the impression that 1.9 threads were no longer
"green threads" and shouldn't behave in this manner since they're
*actual* threads now.
I would be perfectly happy using fork for this, except fork isn't
available on windows and the win32-process gem doesn't look to be a
solution for me (I've already investigated it).
My dev box is a Win7 box, but the clients machine will be a WinXP
machine.
I've included an excerpt where I'm creating the thread in the hopes
that someone can help identify why the UI thread appears to be getting
starved for time. There's not much there, so if you need something
more, please let me know.
Thread.new {
# call extension function
}
processing. I've implemented an extension to put the processing into
C, so all is right the world there.
The issue is that I'm attempting to kick off the processing in a
separate thread to keep the UI responsive to the user, and it isn't
working. I was under the impression that 1.9 threads were no longer
"green threads" and shouldn't behave in this manner since they're
*actual* threads now.
I would be perfectly happy using fork for this, except fork isn't
available on windows and the win32-process gem doesn't look to be a
solution for me (I've already investigated it).
My dev box is a Win7 box, but the clients machine will be a WinXP
machine.
I've included an excerpt where I'm creating the thread in the hopes
that someone can help identify why the UI thread appears to be getting
starved for time. There's not much there, so if you need something
more, please let me know.
Thread.new {
# call extension function
}