I didn't try a front script. Maybe I'll try that.
On Mon, Nov 20, 2017 at 10:56 AM, Trevor DeVore via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On Mon, Nov 20, 2017 at 8:56 AM, Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > That doesn't catch every time
On Mon, Nov 20, 2017 at 8:56 AM, Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:
> That doesn't catch every time we have a debugger drop, unfortunately.
The debugger is probably capturing the message. Did you try defining
errorDialog in a frontscript?
--
Trevor DeVore
Scre
On Mon, Nov 20, 2017 at 8:56 AM, Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:
> or every time a mobile script just aborts.
>
Did you put it in the message path using a library script? If a script
error occurs then errorDialog will be triggered.
--
Trevor DeVore
(703) 785
or every time a mobile script just aborts.
On Mon, Nov 20, 2017 at 9:56 AM, Mike Kerner
wrote:
> That doesn't catch every time we have a debugger drop, unfortunately.
>
> On Mon, Nov 20, 2017 at 9:34 AM, Trevor DeVore via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> On Mon, Nov 20
That doesn't catch every time we have a debugger drop, unfortunately.
On Mon, Nov 20, 2017 at 9:34 AM, Trevor DeVore via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On Mon, Nov 20, 2017 at 8:31 AM Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > Is there a "
On Mon, Nov 20, 2017 at 8:31 AM Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Is there a "universal" error message that is called when something bad
> happens in LC?
See the errorDialog message in the docs .
Trevor DeVore
ScreenSteps
Is there a "universal" error message that is called when something bad
happens in LC? I don't really want to write try/catch blocks for every
command that is dropping me into the debugger in scripts that are supposed
to be running unattended (and on mobile, I'd like to see if I can come up
with a
