Re: NSTimer causes events to be lost
Re: NSTimer causes events to be lost
- Subject: Re: NSTimer causes events to be lost
- From: Guy English <email@hidden>
- Date: Mon, 21 Mar 2005 14:09:02 -0500
John Pattenden <email@hidden> wrote:
> I'm not running at 500fps, to get the animation to run at 30fps the
> rendering code needs to be called about 500 times a second - then Cocoa
> starts to lose its own events..
Uh ... why? If you're only blitting to the screen at 30fps why render
at 500fps? I can only guess you're using some kind of accumulation
technique. Why can't you just pass the "render time" into your
renderer and have it render based on that time? Unless you're doing
everything iteratively you should be able to solve an objects position
for any given time. If indeed you are doing an accumulation trick just
do a for loop over the time samples you're intested in passing each to
the render function.
Guy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden