Thanks guys. Using class methods was a brilliant idea. Solidified my
understanding of when I might want to use them, and when I might want
to use @synchronized as well.
-s
On Sat, Jul 26, 2008 at 7:30 PM, Todd Heberlein <[EMAIL PROTECTED]> wrote:
>> - (id)init {
>> ...
>> timer = [NSTimer scheduledTimerWithTimeInterval:10.0
>> ...
>> }
>
> ...
>>
>> That new instance of course calls init, and suddenly I have two NSTimers
>> running when I only wanted one timer for the whole app.
>
> I think you want to make your timer a global variable and then initialize it
> within a call to a +load or +initialize method for one of your classes. See
> the following link:
>
> http://developer.apple.com/documentation/DeveloperTools/gcc-3.3/gcc/Executing-code-before-main.html
>
> Todd
>
>
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
