I gave it the once over with IE5.5 NS4.08 ns6.0.
NS6 behaves strange indeed, maybe someone can test whether mozilla has the
same problem or not. (Nuno?)
I tried to find a setting that gave a good result on all browsers, I had
expected the result to be smoother if the time used for the distance was
higher, maybe 40 sec or so , but this was not the case, I got the best
result with:
20 seconds 354 pixels 55 sleep value
Strangely this gave a better result than 360pixels, which is devideable by
20.
Of course I didn't test running several animations at the same time.
Taking these results to be correct, we could have a timing system, like
thread, which would run at 55ms, calculating the altered distance, compared
to the expected distance, triggering the run event, and returning a
coöficient, 1.1, or 0.9 etc, which could be used to multiply the distance of
the actual animation.
I notice this doesn't sound very clear, I'll see if I can't work something
out another time.
Cheers,
Richard Bennett
[EMAIL PROTECTED]
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)
Find the DynAPI faq here:
http://sourceforge.net/docman/display_doc.php?docid=656&group_id=5757
Browse the mailinglist here:
http://www.mail-archive.com/index.php3?hunt=dynapi
----- Original Message -----
From: "David Cushman" <[EMAIL PROTECTED]>
To: "dynapi - developers" <[EMAIL PROTECTED]>
Sent: Monday, March 05, 2001 9:23 PM
Subject: [Dynapi-Dev] Timed Animation Example Page
> Greetings All,
> For those of you following the discussions on
> animation and timing, Daniel Aborg suggested a timing
> method using thread that is self correcting for time.
> Very simply, it adjusts the number of pixels to step
> to complete the animation in a given time amount.
> It seems to work very well across the browsers.
> The following link is a demo of that technique for you
> to experiment with. It uses the moveBy command to
> reposition the layer. The "sleep" setting is set to 1
> to make the browser default to the minimum timeslice.
> On IE for example, any setting between 1 and 55 gives
> the same results (number of steps to complete).
> I added in a process delay capability that has two
> levels. The first just runs a math function in a for
> loop every 200 ms and the severe process adds a write
> to screen command, forcing the screen update.
> Interesting Note:
> Under NS6, the severe setting actually stops the
> processing of the layer movement while it updates
> values to the screen. Whatever happened to concurrent
> processing? Anyone have any comments on this?
>
> Here is the link:
> http://www.merlinsworld.net/dynapi_ri_dcexamples/timing02.shtml
>
> Comments anyone?
>
> Dave C. "You Changed What?!?"
>
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail.
> http://personal.mail.yahoo.com/
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
