bobs at twft.com
Thu Mar 29 19:48:46 EDT 2012
Locking the screen can dramatically improve performance for anything which changes what you see in livecode. Progress bars are always changing due to animation. I had the same issue with animated gifs in my spinner standalone.
Calvary Chapel CM
Sent from iPhone
On Mar 29, 2012, at 16:36, Pete <pete at mollysrevenge.com> wrote:
> Thanks Scott and Richard. I think I've got my algorithm to determine when
> to update the progress bar nicely tuned now.
> I'm a little confused by the lock screen thing though. Isn't lock screen
> for when you don't want screen changes to be seen?
> On Thu, Mar 29, 2012 at 4:22 PM, Richard Gaskin
> <ambassador at fourthworld.com>wrote:
>> Pete wrote:
>>> It takes about 2.5 times longer to process my test data with a
>>> progress bar than without one.
>>> I calculate the update interval by dividing the number of records to
>>> be processed by 100 with a minimum of 10 to deal with small data
>>> sets. I guess maybe I can play around with the divisor of 100 to
>>> see what yields the best blend of performance while still showing
>> Yes, the longer interval between updates will help a lot.
>> This is true for all OSes, but even more so on the Mac with the rich
>> rendering required for the Aqua progress indicator.
>> Richard Gaskin
>> Fourth World
>> LiveCode training and consulting: http://www.fourthworld.com
>> Webzine for LiveCode developers: http://www.LiveCodeJournal.com
>> LiveCode Journal blog: http://LiveCodejournal.com/**blog.irv<http://LiveCodejournal.com/blog.irv>
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> Molly's Revenge <http://www.mollysrevenge.com>
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode