On Sat, Jun 23, 2012 at 2:12 PM, wrote:
> Don't forget about locking the screen or the recents.
Oh, yes. Locking the screen made a *huge* difference in building the
output (dozens upon dozens of fields being placed, moved, and filled .
. .) It still takes about 15 seconds to generate 22 pag
he other
way around.
Craig Newman
-Original Message-
From: Dr. Hawkins
To: How to use LiveCode
Sent: Sat, Jun 23, 2012 4:04 pm
Subject: Re: Is there a serious garbage collection problem
On Sat, Jun 23, 2012 at 5:27 AM, Mark Schonewille
wrote:
>
> There might be some scripts
On Sat, Jun 23, 2012 at 5:27 AM, Mark Schonewille
wrote:
>
> There might be some scripts running after you delete a card. To prevent this,
> lock messages before deleting the card:
>
> lock messages
> delete card
> unlock messages
>
> This will probably faster than whatever you're doing now.
Uh,
27;t seen anything like this for several years.
>
> Is there a *serious* garbage collection problem with livecode?
>
> When I delete cards from my output stack, the response time is
> measured in seconds. For a half dozen cards, it's long enough for me
> to get annoyed, and
he PC the application
was working again...
On 23 Jun 2012, at 03:04, Dr. Hawkins wrote:
> I haven't seen anything like this for several years.
>
> Is there a *serious* garbage collection problem with livecode?
>
> When I delete cards from my output stack, the response time
On 6/22/12 9:04 PM, Dr. Hawkins wrote:
I haven't seen anything like this for several years.
Is there a *serious* garbage collection problem with livecode?
When I delete cards from my output stack, the response time is
measured in seconds. For a half dozen cards, it's long enough for
I haven't seen anything like this for several years.
Is there a *serious* garbage collection problem with livecode?
When I delete cards from my output stack, the response time is
measured in seconds. For a half dozen cards, it's long enough for me
to get annoyed, and actually laun
