So, those of you who were beta testers, I have one question - has MACR
continued with the short error messaging as a default, requiring us to
either to put an ini file on our CDs that allows full lingo error
messages, or in the case of shockwave, makes us walk some schlub
through installing a shockwave ini file, in order to get a descriptive
bug track? One of my pet peeves - developers who want their apps to
fail with a simple "script error, continue?" ought to be the ones to
jump through hoops to make that error short error message appear... the
rest of us would like some clue as to what makes the app fail. I can't
tell you how many hours I've wasted tracking down the source of a bug
that only happens for certain users on certain machines in shockwave.
It's not as big a deal on CDs, because you can include an ini file.
Relying on a Marketing-tard to get a shockwave ini file up and running
which lets your app say "object expected" instead of "contact the
developer" is a real pain in the nether-regions.
-Kurt
[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!]
- RE: <lingo-l> Debugging Kurt Griffin
- RE: <lingo-l> Debugging Mark R. Jonkman
