Peter Haworth wrote:
My debugging showed that the setting of fonts was causing the standalone to
abort silently....
IMNSHO that's a bug. Errors in execution should be reported by default,
with the ability to have mystifying failures happening silently only as
an option.
But for reasons I don't understand, the inclusion of the Error Reporting
dialog is turned OFF by default, making it close to impossible to know
when execution errors happen in standalones.
This is extra important given that the LiveCode IDE alters the structure
of your mainstack to include the libraries, backscripts, and other
components needed to support the things it does include. This means
that the boot behavior of most apps will be different in a standalone
than in the IDE, giving rise to a wide range of potential issues whose
causes cannot be known.
I've submitted this as a feature request, but I'm not sure that many
others appreciate the number of hours that would be saved by LiveCode
developers if we could know about errors in standalones as soon as they
happen:
Include revErrorDisplay by default
<http://quality.runrev.com/show_bug.cgi?id=9629>
In the meantime, we need to remember to manually include the Error
Reporting dialog in the Standalone Builder Settings in order to know why
things aren't working.
--
Richard Gaskin
Fourth World
LiveCode training and consulting: http://www.fourthworld.com
Webzine for LiveCode developers: http://www.LiveCodeJournal.com
Follow me on Twitter: http://twitter.com/FourthWorldSys
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
