At 08:08 -0500 02/22/2002, Jason Gruhl wrote:
>I have a project in which many people are doing
>test cases on. Not all possess the director
>application and thus they must test of an
>executable. Two different computers run the same
>executable at different times and one gets script
>errors and one does not. One is XP and the other
>is windows 98 2nd edition... There is some
>minimal fileio... My question is I assumed these
>two should act the same, but they don't, any
>ideas?
Yeah. Don't release on XP, which sucks even mroe than most MS products. ;)
More usefully, it might be a permission issue (who can read
from/write to what); or it might be an issue which is cropping
(crapping?) up more and more on XP when dealing with paths to files
which have more than 127 characters in them (there are lots of
failures being logged there). To test the former look at permissions
on XP. To test the latter look at path lengths.
>Another question is: Is there a way to get
>the message on an execuatble to be more verbose in
>the script error message.
Oh gods.
Sort of, but not really.
Create a text file named after your projector, but with the extension
ini. So if your projector is "My groovy program.exe", your ini file
would be "My groovy program.ini". With me so far?
OK. Inside that file put in these lines:
[lingo]
DisplayFullLingoErrorText=1
This file is then saved and placed alongside your projector. In
theory this helps.
In reality it doesn't. Read on.
For starters, if you already have an ini file sitting alongside your
Dir85 program named (for instance) "Projector.ini", every time you
save a projector named "Projector" that ini file will get wrapped
into the package, and *nothing you do will override its settings*.
So? So by default the line DisplayFullLingoErrorText is commented
out, meaning you can't change it later.
But it gets worse.
When you actually create a projector, or shock a movie, or protect a
movie, its scriptText is stripped away. So the "full error text" that
will appear will not actually contain any more useful information
than what you're getting now.
If you use an unprotected DIR file you will actually see the lines of
code that are going wrong and that will be helpful. But this
particular ini file setting, where all-in-one projectors, DCRs and
DXRs are concerned, is worthless.
--
Warren Ockrassa | http://www.nightwares.com/
Director help | Free files | Sample chapters | Freelance | Consulting
Author | Director 8.5 Shockwave Studio: A Beginner's Guide
Published by Osborne/McGraw-Hill
http://www.osborne.com/indexes/beginners_guides.shtml
[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!]
