Can anyone confirm this possible bug ?

[Mike Bonner]

The name of the stack is "revErrorDisplay"  you might check the openstacks
to see if its there somewhere. Maybe it has been minimized? Though mine
un-minimizes on each error, so off the screen is more likely. It doesn't
close between errors and is persistent in whatever location its at.

On Wed, Aug 29, 2012 at 3:00 AM, Alex Tweedly <alex at tweedly.net> wrote:

> That's it Mike !  Thank you !!
>
> I had Script Debug Mode off - unintentionally, and had forgotten there was
> such a thing.
> Whn I turned it back on, then the error appeared as expected in the bottom
> pane of the editor window.
>
> No idea what has happened to my error window that should appear when debug
> mode is off; I can't find any windows that appear to be off-screen. (But
> maybe it's gone again by the time I open the msg box and look ??)
> What is the name of that window ?
> Any settings for it I could check ?
>
> Thanks again
> -- Alex.
>
> On 28/08/2012 17:58, Mike Bonner wrote:
>
>> 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 tweedly.net>  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 lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
>>> http://lists.runrev.com/****mailman/listinfo/use-livecode<http://lists.runrev.com/**mailman/listinfo/use-livecode>
>>> <**http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode>>
>>>
>>>
>>>  ______________________________**_________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode>
>>
>
> ______________________________**_________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode>
>