At 03:31 �� 20/2/2002 +0100, you wrote: >Dave wrote: > > If you know how long it takes to carry out task X, and that you can carry > > out task X a certain amount of times between each frame being read out for > > display, simply make the program aware of that interrupt, and carry out > > the task right after the frame has been drawn, confident of finishing it > > before the next interrupt. > >No, the point is: there is no suitable interrupt. > > > On other architectures it's easy to have two video buffers, and alternate > > between them - I don't know how easy it is to move the start of screen > > memory on the QL and derivitives (on the vanilla QL it's prolly > > impossible) but hey, no problem - we'll find a way ;) > >Double buffering works quite well on the original hardware (as the >(IIRC) KAOS games proved). However, all other platforms don't have a >second video buffer (when QPC did still run with Minerva I did >actually emulate the second screen, but I removed that for SMSQ/E). > >Marcel
I see you are still UP! Presumably working on QPC v. 5 with Sound, Sprites, Nice CLI and a decent filesystem????? Hee Hee Phoebus
