OIC I have had problems also where a script stopped dead in it's tracks because
something was wrong but it didn't visibly throw an error. Certain sqlYoga
commands will do this, for instance if you use sqlquery_set on a query object
that doesn't exist yet.
Bob
On Mar 4, 2012, at 7:30 PM, Sieg Lindstrom wrote:
> Thanks, Kay. This was running in the IDE. I tried starting the IDE, then
> opening the stack. Still didn't work OK.
>
> Then I tried saving as a standalone and that revealed the apparent problem,
> which was two lines of code in another handler in the stack script. This
> handler also ran OK previously under RunRev.
>
> The two lines were these; not contiguous in the script.
>
> put "; . {}" into findString
>
> put "; . {w, w, w}" into findString
>
> Seems the compiler didn't like the semi-colons (keyword) at the front of the
> literal.
>
> FYI, two interesting things about this:
>
> 1) there were other put commands in the script in which a semi-colon led a
> literal, and they compiled OK.
>
> 2) Eventually, simply retyping the lines solved the problem.
>
> Sieg Lindstrom
>
> On Mar 3, 2012, at 9:29 PM, Kay C Lan wrote:
>
>> Is this in a standalone or a stack you are running in the IDE.
>>
>> There is a know problem with the start-up sequence of 5.0.2 that effects
>> some stacks when run in the IDE. To figure if this is effecting you, start
>> the IDE, then open your stack and see if it works OK. If it does, then this
>> was the problem. If so you just can't open your stack by double clicking
>> it. Hopefullly this will be resolved in the next update.
>>
>> HTH
>>
>> On Sun, Mar 4, 2012 at 12:10 PM, Sieg Lindstrom
>> <[email protected]>wrote:
>>
>>> My second post tonight while I'm thinking of it. I have an app that ran
>>> flawlessly under RunRev. Now, using LiveCode 5.0.2, a handler in a button
>>> script that calls another handler in the stack script returns a "can't
>>> find handler" error.
>>>
>>> It was easy to fix by moving the "unfindable" handler into the button
>>> script, but shouldn't a button be able to call a handler in the stack
>>> script? It worked before, hasn't been modified and all variables are
>>> properly made global. ????
>>>
>>> Thanks.
>>>
>>> Sieg Lindstrom
>
> _______________________________________________
> use-livecode mailing list
> [email protected]
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
