jared_kipe> First off why
I'm updating a classic app which does a monster computation, (in response to "new"). Idle events, clock ticks, (and of course frontmost), are looked at to judge how greedy to be in the old app. I can handle figuring out frontmostB(), but the idle stuff is not happening.
So, a couple reasons why: One, I guess laziness, but it would be nice to keep the same paradigm, if not the same exact code, while I'm updating the whole UI thing and UI events to carbon or cocoa depending on compile, (got that stuff mostly done). Two, beyond playing nice with others, it's pretty important that the app itself stays responsive in case the user does something in menus or open windows while the monster computation is going on. How that's supposed to work with the new 'events are callback-only' type thing in cocoa I just don't see.
>second off NSThread has -setThreadPriority: method to play nicer with other running operations.
I have the feeling you're going to say that I need to use NSThread, period, no other, like "normal" way to go? I probably shouldn't say "normal"-- I have no idea what's normal anymore!

Thx.