Wheneve you use a wait icon as a timing device you're going to see different 'timing' on different computers and under different circumstances. The wait icon waits until the contents of a display icon has loaded before it starts timing.
It's better to use a conditional or SyncPoint()/SyncWait(). BTW, the correct way to use the latter is to put a single SyncPoint() at the beginning of the image sequence then use SyncWait() relative to the syncpoint between the images. For example, the first SyncWait() would be 1, the next one 2, the third 3, and so on.
John Eustis Williams wrote: > . . . > > However, each picture is supposed to be displayed for one second and then > erased with a one second wait in between displaying the next picture. > > In Authorware while developing the a5p file this timing scheme works fine > with the new library. The resulting a5r file with the library packaged > internally works fine with this timing. However, when the shocked files are > run for the first time in the web browser the pictures display for about 5 > seconds before erasing. If the shocked files are run again without clearing > the browsers cache the timing is now correct, displaying for 1 second > before erasing. > > This initial delay I can understand because the browser reacts quicker with > a cachced verison. . . . -- Grace Daminato
Macromedia Evangelist
Interaxys New Media voice: 905.542.2404 e-mail: grace@interaxys.com
-- The AWARE List http://www.e-media.nl/aware/index.html
Search the Archives http://www.e-media.nl/aware/search.html
Netiquette: - Use descriptive subject fields - Use subject prefixes (A5 , A5Mac , A5Web , KO , UCD , OT)
Authorware
Grace Daminato