Anomalous Script behavior

Peter Haworth pete at lcsql.com
Fri Jul 24 17:33:00 CEST 2015


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 example but it's been a while since it happened to me.

I would add some code to your tracking mechanism to track the value of any
critical variables, especially those that are passed as parameters to other
handlers.

On Thu, Jul 23, 2015 at 10:16 PM Peter Bogdanoff <bogdanoff at me.com> wrote:

> 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 35,655 characters. Is there a limit to the number
> of characters?
>
> I put in breakpoints that are sometimes reached, sometimes not.
>
> It’s a handler that is being called by callbacks in a player as the media
> plays, so it’s difficult to debug while the media is playing. So I put some
> code in to put data into a field when those lines of the script are
> reached. Then I can see the progression through the script in real time.
> When it’s not working properly, while the handler IS receiving the callback
> calls, that field stays empty.
>
> Any ideas?
>
> Peter Bogdanoff
> UCLA
> _______________________________________________
> 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
>


More information about the use-livecode mailing list