smf wrote: > Probably a combination of both would be useful. Some of the int 16h calls return immediately and you would not want that to trigger a scan of the screen if it's sitting in a loop. Maybe a timer to measure time from last INT 16h call - this way, if it's sitting in a tight loop, we may refresh the screen from time to time, but not on every access which would not be necessary. Regards, Michau. Message was sent through the cbm-hackers mailing listReceived on 2017-10-17 17:00:03
Archive generated by hypermail 2.2.0.