Am 25.04.2006 um 10:35 schrieb <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>:

Hi,

I’m using the ProgressDialog Version 0.2 parent script by Luke Wigley, and strangely, on some computers it doesn't work for no apparent reason. The script calling it just stops executing without throwing an error... This is the case on two out of six PC's I've tried it on, all running XP SP2 and a fully up-to-date IE (including the nasty active-X security "fix").

it seems, that you are trying to deliver for the browser.
without any knowledge of the script itself (I have my own ones, which have a similar approach as Luke's excellent behaviors) I'd say you may have an xtras problem here. compare the xtras folder of the computers where it doesn't work correctly to the ones, where it does work. (the shockwave xtras in the global shockwave install folder (something like: C/WINDOWS/ System32/Macromed/Shockwave 10/Xtras) and the custom xtras in the Users local folder ( something like: C/Documents and Settings/ Username/Application Data/Macromedia/Shockwave/Xtras)

I suspect one of the NOT standard installed xtras is missing, my guess is the font asset xtra, which we IL folks tend to use to get a list of installed fonts in order to render text to image...

You must mark that xtra as "Download if needed" in order to install it on the users machine.

the reason it doesn't throw an error may either be caused by Luke's script preventing script errors due to decent error checking or due to the annoying fact, that someone had the idea, that it would be a good idea to surpress the first 10 errors in shockwave and simply proceed with the movie as if the error didn't occur, instead of exposing this functionality of exception catching to lingo. You can disable that behavior with the:

[Lingo]
DisplayFullLingoErrorText=1

directive in the shockwave.ini file.

Once you place a file named exactly "shockwave.ini" with the above content in the same folder as shockwave is installed (right next to DPLib and IMLib) a more descriptive error message will be displayed at the first script error encountered.
This error message may lead you to the source of your problem.


---------------------------

  |||
a¿ex



[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email 
[email protected]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for 
learning and helping with programming Lingo.  Thanks!]

Reply via email to