> but the summary is that it looks like it will in fact do *some* > processing behind the scenes to a point, and then it hits a wall and > stops indefinitely until the mouse is moved. As if a small buffer is > being filled, and then it as to wait.
This is exactly what it does. Processing goes on in the background. When there is an idle event (processor is free), then it sucks the output out and displays it. This is how tasks like this ought to be done. The issue is that for some reason, idle events aren't generated by it just sitting there, idling. This happens on all windows versions, apparently. Moving the mouse or otherwise making an event sends a WakeUpIdle as part of its event queue management, thus launching the things that should be done on an idle event. Solution will probably to have a timer that sends a WakeUpIdle event every second or two, to generate an idle event. This is what I am working on at the moment. Best wishes, Robert _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
