At 02:08 �� 20/2/2002 +0000, you wrote:
>On Tue, 19 Feb 2002, Marcel Kilgus wrote: > > > Well, there is just no way to avoid flickering. On fast machines the > > possibility that flicker appears gets smaller but it's never zero. > >I slightly disagree. Not much, just a little bit. > >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. If there's too much activity to redraw in the >time available, drop the lower priority redraws. Well something like that can be done on the original QL as both Nasta and Marcel explained. Additionally don't forget that the "vanilla" QL has two Screen memory areas (SCR0 and SCR1) (Both of them usable with Lau's /TFS Minerva ) and Auroras have 3 (The two standard plus the hi-res one so definately you could do some tricks there) The thing is (I repeat) that there's no "legal" way to do things like that and that's where toolkits or a QL equivalent of Mac's Quickdraw should come in... (You hear that Nasta? Put it in the pipeline for Aurora II). >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 ;) See above. Phoebus >Dave >ql.spodmail.com
