On Mar 6, 2005, at 7:29 PM, Jake Pietrykowski wrote:
I've attempted using idle handlers to count seconds with an ASStudio
application. Counting seconds decreases application performance
severely,
and while my application was a GUI front end for a FileMaker, in the
process, I managed to bring my FileMaker clients on the network to a
screeching halt...and I was just developing the application.
I'd stay away from using the idle handler. What I did is, for example,
i was
counting the elapsed time, i just but a button to click to
re-calculate the
time as desired. Then it's on-demand, and not eating up the
CPU's...and i my
case...choking the network.
Hello,
Thanks for the suggestion. I have found it is drawing to the screen
from any handler, not calling the idle handler per se, that decreases
performance. If your idle handler merely counts the seconds (or
whatever) in an internal variable, but does not draw on the screen, it
can be very fast. Drawing to the screen is very slow in AppleScript
Studio, so I stay away from gratuitous drawing on the screen, and
optimize where I can, such as an Update button as you described. I
avoid animated progress indicators for the same reason.
