libURL Script Error After Upgrading to LiveCode 5.02

[Mike Bonner]

If this is like some of the stuff (such as the thread about choosing the
browse tool from within an openstack or preopenstack handler) A workaround
was to move the affected code into a separate handler then from wherever
you were doing the original call from, do a send in time.  It doesn't take
much delay to get around stuff (assuming it IS the same issue..)  Seems
like the workaround should be fine in a standalone too.

On Fri, Dec 30, 2011 at 11:47 AM, Bob Sneidar <bobs at twft.com> wrote:

> Ooooh good point... What if this happens with standalones?
>
> Bob
>
>
> On Dec 30, 2011, at 10:29 AM, Gregory Lypny wrote:
>
> > Hi Guglielmo,
> >
> > Thank you for your response.  I will do what you say while revising my
> app, but does it mean that the standalone will not be affected?
> >
> > Gregory
> >
> >
> > On Fri, Dec 30, 2011, at 1:00 PM, Guglielmo wrote:
> >
> >> Yes, same behavior for me with different handlers ...
> >> ... there must be an error on Livecode 5.02 ... it seems to start your
> >> application before he has finished loading its own modules :(
> >>
> >> If you first open Livecode 5.02, wait until Livecode is completely
> started
> >> and then you start your application ... no problem and all work fine.
> >>
> >> Hope this help,
> >>
> >> Guglielmo
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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
>