Re: Rob: More trouble with PD-source
Robert Craig wrote:
> By defining a private variable "StatusProc", you are causing
> the routine id of "StatusProc" to be -1. This turns off the
> (frequent) callback to StatusProc(), so things work much better.
> I think I mentioned already that things worked much better
> when that callback was turned off.
OK thanks, I think I understand now.
> Yes. The video capture option doesn't consume much time.
> You can't even tell it's runnning. A time-shared
> task writes frames of data to disk when there's nothing else to do.
> A profile_time on Language War shows that about 90% of the time it's just
> sitting in the scheduler waiting for the clock to advance so
> it can run the next task.
Right have it as an *option*, we wouldnt want to use it all the time. It can
create huge playback files to disk.
> I hope so. There are a few places where I lose a tiny bit of
> performance in order to work around a Watcom bug.
Right.
> Yes, I'll probably do that.
> I want to make sure everything is rock solid before
> I start inserting small optimizations.
Fantastic... sounds great. Later when it's time to implement real thread-safety
and extend + modify the existing task API, you'd probably have to make some
significant changes to the existing code; perhaps that would eliminate this
problem all together.
> Regards,
> Rob Craig
> Rapid Deployment Software
> <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
Regards,
Vincent
|
Not Categorized, Please Help
|
|
