Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stanford.edu!agate!fugitive.berkeley.edu!izumi
From: izumi@fugitive.berkeley.edu (Izumi Ohzawa)
Newsgroups: comp.sys.next
Subject: Re: main event loop
Message-ID: <1991Mar11.080607.26410@agate.berkeley.edu>
Date: 11 Mar 91 08:06:07 GMT
References: <228@qt.cs.utexas.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Organization: /etc/organization
Lines: 28

In article <228@qt.cs.utexas.edu> tph@cs.utexas.edu (Pow-Hwee Tan) writes:
>
>    Specifically, I would like a routine I wrote to be called each time
>through the main event loop.  I have tried using DPSAddTimedEntry with an
>interval of 0, but the animation done by the routine called is still jerky.
>While the 'jerkiness' may not be avoided totally with a heavy load, I would
>still prefer a more direct call from the main event loop to my routine.

Apologies if you know this already, but do you have

NXPing();

in the method that is called each time the TimedEntry is executed?
That is the standard way to fix 'jerkiness' problems with
animation.

Windowserver normally buffers DPS code sent to it, and executes it
in bursts causing jerkiness.  Overriding 'run' methond may not
fix anything if the jerkiness is due to windowserver buffering.
NXPing() essentially flushes the buffer and blocks until the piece of DPS
code sent to the windowserver is executed.


-- 
Izumi Ohzawa             [ $@Bg_78^=;(J ]
USMail: University of California, 360 Minor Hall, Berkeley, CA 94720
Telephone: (415) 642-6440             Fax:  (415) 642-3323
Internet: izumi@violet.berkeley.edu   NeXTmail: izumi@pinoko.berkeley.edu