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? Pete On Thu, Mar 29, 2012 at 4:22 PM, Richard Gaskin <ambassa...@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 > > progress. > > 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@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode> > > -- Pete Molly's Revenge <http://www.mollysrevenge.com> _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
