Quote:
Originally Posted by Jume
so is this a good practice to have this timer running at all time and waiting to the right hour to come?
|
I can't see why it's a bad practice.
I observe that there're Time Manager functions inside CoreServices framework, but all of it has been deprecated since Mac OS X 10.4, so they advise to use Carbon Event Loop or NSTimer.
My understanding of NSTimer is it will run based on the schedule of the main application event loop, so I don't think it's something that will consume lots of resources, besides the fact that you're doing this on the desktop.
