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 thus
> it falls through to the backscript handler. Of course, this is all
> purely conjecture at the moment - I haven't had a chance to check it
> directly yet today!
I could understand the errant script (the button) being omitted from the
message path during an error condition, but what surprised me is that
the stack's script was also omitted.
Exploring further, I created a stack which I put into the message path
with "start using", which has:
on errorDialog
put the name of me && the params
end errorDialog
It was ignored too. :\
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, there definitely sounds like something fishy is going on
> here so could you file a bug report with your findings and we can
> look into it more deeply.
Thanks - done:
<http://quality.livecode.com/show_bug.cgi?id=17403>
FWIW, this behavior is the same when I test with the oldest version I
have installed, 6.7rc2.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
_______________________________________________
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
