Mark Waddingham wrote:
> The IDE engine itself doesn't have any special handling for errors
> (relative to the standalone engine) - however, the IDE must be doing
> something *somewhere* as the part of the engine which implements the
> engine-side part of the debugger is distinct from the part
On 2016-04-14 17:06, Richard Gaskin wrote:
It's almost like the IDE engine has had special handling added at some
point to send errorDialog messages directly to one particular IDE
script.
To be fair, it does say in the dictionary under 'errorDialog':
Note: The errorDialog message is only sent
Mark Waddingham wrote:
> When the script debugger is active, errors indirect via a different
> message (traceError) - so my hypothesis was that the debugger is
> intervening and causing the target of the errorDialog message to
> change so that your button is no longer in the message path, and
On 2016-04-14 16:22, Richard Gaskin wrote:
What I get in the message box is just two lines:
- the errorDialog handler in revbackscriptlibrary
- mouseup from the button that starts the execution path.
What could cause all other scripts to be bypassed to favor one
particular backscript?
My
Mark Waddingham wrote:
> On 2016-04-13 22:46, Richard Gaskin wrote:
>> Ralph DiMola wrote:
>>
>>> It works in a library stack. In fact it also catches IDE errors.
>>
>> Thanks. I found the culprit: I hadn't yet turned off "Debug Mode"
>> (still don't know why the default is to create yet one
On 2016-04-13 22:46, Richard Gaskin wrote:
Ralph DiMola wrote:
It works in a library stack. In fact it also catches IDE errors.
Thanks. I found the culprit: I hadn't yet turned off "Debug Mode"
(still don't know why the default is to create yet one more difference
between IDE and runtime,
Ralph DiMola wrote:
> It works in a library stack. In fact it also catches IDE errors.
Thanks. I found the culprit: I hadn't yet turned off "Debug Mode"
(still don't know why the default is to create yet one more difference
between IDE and runtime, but oh well...)
--
Richard Gaskin
, 2016 4:22 PM
To: How to use LiveCode
Subject: errorDialog broken?
Many years ago I thought I could use the errorDialog message to catch throw
statements, but when I try that here in both v6 and v8 I find all
errorDialog handlers are ignored
- EXCEPT -
...for the one in LC's revbackscriptlibrary
1
Many years ago I thought I could use the errorDialog message to catch
throw statements, but when I try that here in both v6 and v8 I find all
errorDialog handlers are ignored
- EXCEPT -
...for the one in LC's revbackscriptlibrary
1. Why?
2. How?
--
Richard Gaskin
Fourth World Systems
