On Mon, 31 Jan 2005 20:00:08 -0800, John Stiles <email@hidden> wrote:
> On Jan 31, 2005, at 7:05 PM, Guy English wrote:
> > The trouble is you want to control the run loop - otherwise
> > you're stuck only updating as fast as you can fire off timers.
> If you set the timer delay to 0.0, AppKit will call your timer
> constantly without waiting.
Yeah ... It's been a while but I thought at one point it either
coalesced ticks, drop them, or did something else I didn't like -
possibly stall waiting for a run loop source that would sometimes
block longer than I could afford to let it. If it can handle things
real time-ish now then I agree it's a much better idea.
You'll likely just want to subclass NSApplication and override
sendEvent then. Dispatch based on ui mode and you're set. I think. Is
there something I'm missing about why you can't do this?
> And frankly, imagine you're "unlucky" could only get the timer to fire
> 200 times/second. 200FPS is not too shabby.
Bah! What's the point of sinking all that money into my video card if
I can't run Quake I at twice that speed! :)
Later,
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
