Revolution is very slow to refresh fields. How can I speed it up?

[Eric Colvin]

Like magic!  Thank you both very much for your suggestions.

I'm sorry, I must confess there wasn't any strong reason to want to do this;
I was just exploring the environment.  But it is most reassuring to know
that a solution is generally close at hand.  Thanks again,


Eric


-----------------------------------------------------------------------

I assume you're on OS X. The problem you describe isn't Revolution's
fault, it is the operating system. This is from the What's New file:

> Issue:  Rapid changes in stack windows may not be seen on OS X
> systems because of the way OS X buffers window contents.

>Workaround:
> Use a very short "wait" command after the change, then continue with
>  the handler.

Revolution supports milliseconds, so your wait could be as little as:

   wait 1 millisecond


-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com
_______________________________________________
metacard mailing list
metacard at lists.runrev.com
http://lists.runrev.com/mailman/listinfo/metacard



> From: Ken Ray <kray at sonsothunder.com>
> Reply-To: Discussions on Metacard <metacard at lists.runrev.com>
> Date: Thu, 30 Mar 2006 07:38:26 -0600
> To: MetaCard List <metacard at lists.runrev.com>
> Subject: Re: Revolution is very slow to refresh fields.  How can I speed it
> up?
> 
> On 3/30/06 6:03 AM, "Eric Colvin" <EricMColvin at telus.net> wrote:
> 
>> I¹ve just started playing with Revolution. I was an enthusiast for Hypercard
>> in a previous life.
>> 
>> One thing I¹ve hit upon early on that frustrates me a little.  Though
>> Revolution is far newer, and ought to be faster since it loads into memory
>> rather than writing to disk, I find it way slower at refreshing text fields
>> than Hypercard ever was.
> 
>> Surely there must be some way I can persuade the field to refresh more
>> frequently and and display everything put into the field?
>  
> Adding "unlock screen" in your repeat loops just before "end repeat" will
> force an update after every number, but significantly slows down the loop
> processing (seems to about double the time it takes). For example, without
> the unlock screen, I get:
> 
>   54 : 6
> 
> With the unlock screen, I get:
> 
>   108 : 11
> 
> 
> I'm just curious... for what reason would you need to do what you're asking
> for? One of the reasons Rev is so fast is that it tries to minimize screen
> updates as often as possible, so maybe backing up and explaining what you
> need to do would help us provide a better solution.
>  
> Thanks,
> 
> Ken Ray
> Sons of Thunder Software
> Web site: http://www.sonsothunder.com/
> Email: kray at sonsothunder.com
> 
> _______________________________________________
> metacard mailing list
> metacard at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/metacard