Thanks again Guglielmo,
That’s a relief. The Rev team needs to get its act together. There are too
many such incidences.
Gregory
On Fri, Dec 30, 2011, at 8:19 PM, use-livecode-requ...@lists.runrev.com wrote:
> No, fortunately the standalone applications seem to work normally (/...
> tried
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
>
No, fortunately the standalone applications seem to work normally (/...
tried on OS X 10.6.8 and Win
Yeah, that same thread I mentioned discussed the problem being with 5.02
also. Just hadn't noticed if a temp workaround had been mentioned in this
thread yet or not. Surely seems buggy to me.
On Fri, Dec 30, 2011 at 12:26 PM, Bob Sneidar wrote:
> Aye there are workarounds for almost everything.
Aye there are workarounds for almost everything. I think we were just
discussing how the behavior only began with a recent release of Livecode, and
it may be a bug.
Bob
On Dec 30, 2011, at 11:21 AM, Mike Bonner wrote:
> If this is like some of the stuff (such as the thread about choosing the
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
muc
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
>
>
>
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
Gregory Lypny wrote
>
> The following two lines used to work fine in a startup script.
>
>libURLSetLogField the long id of fld “Connection Log" of card
> "Connection" of stack “Headquarters"
>libURLSetFTPListCommand “NLST”
>
> Today I upgraded to version 5.02 of LiveCode and I get the f
Hello everyone,
The following two lines used to work fine in a startup script.
libURLSetLogField the long id of fld “Connection Log" of card "Connection"
of stack “Headquarters"
libURLSetFTPListCommand “NLST”
Today I upgraded to version 5.02 of LiveCode and I get the following error
mess
