Re: Anomalous Script behavior

Hi, I am still wrestling with a bug in LC 7 (quoted below if you want to read—but not necessary). It’s very difficult to reproduce in a sample stack. LiveCode has offered to fix it with credits from the Business program. I do realize that there are long-term and short-term bugs in the IDE that

RE: Anomalous Script behavior

eeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Peter Bogdanoff Sent: Wednesday, September 23, 2015 4:50 PM To: How to use LiveCode Subject: Re: Anomalous Script behavior Hi, I am still wrestling with a bug in LC 7 (quoted b

Re: Anomalous Script behavior

This is the issue I was having with a stack with a player that sends callbacks that a script handler doesn’t seem to respond to… LiveCode 7.1.0 dp1 An update. I was able to isolate the problem. SAVING the stack sets things aright, for awhile... This is how my script should work: 1. I load an

Re: Anomalous Script behavior

Mark, I tried it in LC 6.7.7 RC1 and did NOT see the problem. (The same stack works properly in 6.3.1.) Doubting my sanity, I went back and tried the very same stack in 7.1. RC1 and saw the problem immediately. The script just stops executing. The player continues to send callbacks with

Re: Anomalous Script behavior

@lists.runrev.com Sent: Fri, Jul 24, 2015 1:16 am Subject: Anomalous Script behavior Using LC 7.1 dp1 Part of a script sometimes doesn’t function—sometimes it works just fine. Sometimes it refuses to continue to execute the rest of a handler. This refusal will happen over and over until some point in my

Re: Anomalous Script behavior

Craig and Peter, Thanks for your replies. Yes, I’ve seen this happen other times, but then it does just go away. Here I’m seeing it reoccur over and over... I tried the same script in LC 6.1.3 and it seems better there, but will do more testing. It could be that there is an unexpected value

Re: Anomalous Script behavior

I've run into situations like this and it usually seems to be caused by an unexpected value in a variable passed to an lc function or command which causes it to silently quit and stop the rest of the calling script from executing. Hard to define what unexpected means and I'm trying to think of an

Re: Anomalous Script behavior

Hi Mark, Unfortunately, I don't recall the exact circumstances where this happened because it's been a while. I seem to remember it was a call to one of the datagrid library handlers with a bad parameter that caused the handler containing the handler to stop executing with no error message shown.

Re: Anomalous Script behavior

Hi Peter, Do you see a similar thing in 6.7? The reason I ask is that if the problem is only occurring in an a handler being invoked by the engine as part of callbacks set by the callback property on a player it could be something to do with that specific case. The player implementation on

Anomalous Script behavior

Using LC 7.1 dp1 Part of a script sometimes doesn’t function—sometimes it works just fine. Sometimes it refuses to continue to execute the rest of a handler. This refusal will happen over and over until some point in my testing it starts working again beautifully. It’s a group script with