Anomalous Script behavior
bogdanoff at me.com
Sun Jul 26 02:27:06 EDT 2015
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 apparently valid parameters (a digit) that do invoke the handler, but that handler won’t continue. No errors, no nada.
We really, really, really want to move to LC 7 for English/Chinese language and Unicode (Chinese looks great in 7, bad in 6). People in China are begging for us to make available our Music History program in China. We are happy to see the improved player in the newest version of LC as all our audio is on a remote server and the Chinese mostly use Windows.
As the Thermian Mathesar with fist over heart cries to Jason Nesmith in Galaxy Quest, “You are our last hope!"
On Jul 24, 2015, at 9:42 AM, Mark Waddingham <mark at livecode.com> wrote:
> 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 Mac changed completely from 6.7 onwards...
> Sent from my iPhone
>> On 24 Jul 2015, at 06:15, 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
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode