Re: Optimizing NSRectFill
Re: Optimizing NSRectFill
- Subject: Re: Optimizing NSRectFill
- From: "Michael Ash" <email@hidden>
- Date: Sat, 20 Dec 2008 21:15:26 -0500
On Sat, Dec 20, 2008 at 4:47 PM, Jean-Daniel Dupas
<email@hidden> wrote:
> So I think that you're right (and that everything is synchronous) but I also
> think that the 'flush results to screen' blocks until the screen is ready
> and so limit the number of redraw to the refresh rate of the screen.
> If this is effectively the case, your timer trick will not be very helpful.
As long as the timer's time interval is less than the screen refresh
interval (and the technote says to simply assume 60Hz and that most
drawing doesn't need more than 30Hz, so that's easy enough to assure)
then it will work. And even if the timer is more, it will depend on
the behavior of the event loop. If the event loop is smart it will
process all queued events before running the next timer, in which case
the technique will work even for a zero-interval timer, but I don't
know if it actually works this way.
Mike
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden