Can anyone confirm this possible bug ?

Mike Bonner bonnmike at
Tue Aug 28 12:58:49 EDT 2012

If I have script-debug mode on execution stops and the offending line and
error message is shown in the errors pane at the bottom of the script
window (as expected).

If script debug is off, an error window pops up saying handler not found
with a can't find handler error also as expected.

Is it possible you have debug mode off and your error window is offscreen
or not coming to the front?

On Tue, Aug 28, 2012 at 10:35 AM, Alex Tweedly <alex at> wrote:

> Is this a bug, or a feature, or just something in my environment ?
> Create a new stack, add a button, and make the button script be
>> on mouseUp pMouseBtnNo
>>     put "we get here"
>>     trythis(1)
>>     put "but do we get to here"
>> end mouseUp
> (Yes, I know it's wrong - that's the point :-)
> Compile this script - no error.
> In the card script, put
>> function trythis p
>>     return 1
>> end trythis
> and compile this, then click the button.
> It outputs the first line (i.e. "we get here") and then just stops.
> silently.
> If you correct it to
>     get trythis(1)
> then it all works OK.
> Does this happen for others, or just me ?
> Shouldn't there be some kind of error flagged when the button is clicked,
> to show that a function has been called as though it were a handler ?  Or
> at least to warn that execution has just stopped in mid-flight ?
> Thanks
> -- Alex.
> ______________________________**_________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the use-livecode mailing list