IMNSHO it is insane to ship a project with a known bug by disabling the
error message. How can any of *us* predict whether it will affect the
project when we don't know what is causing the error or the nature of your
project?

I repeat my advice from the other day:

Create a text file called <projectorName>.INI with the following in it:

[Lingo]
DisplayFullLingoErrorText=1

If your EXE if name "Mything.EXE", then name the INI file "Mything.INI"

That will at least give the user a more meaningful error message that might
help diagnose it. Ask the user to take a screen shot of the exact error
dialog.

I am assuming that you are using D8. I don't know if
DisplayFullLingoErrorText=1 works in D7.0.2.

Bruce


>Hi. I'm coworking on a project where every part of the production process
>has suffered delays, except the mastering deadline.
>
>Now I do not usually even consider things like this, but now there's a real
>risc that the product will have some bugs (especially an elusive one, which
>throws a seemingly insignificant Script error, everything works as it should
>even if you 'continue'). Now I gather I could bypass this error by using
>
>on alerthook me, err, msg
>  dosomething
>  return 1
>end
>, which as far as I can tell would make the script error alert invisible AND
>"click" continue.
>
>Now I have not done this ever..., yet an am slightly nervous, does anyone
>know of any things that this could impact on (run time bug related errors,
>where the user should not click continue).
>
>As far as I can tell, it does not interfere with buddyapi's baMsgBox, and
>baMsgBoxEx, which both are in use.
>
>Feel free to share knowledge, experience and hunches.




[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/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