I'm trying to understand when to use exception handling when developing Cocoa
applications. In regard to this, two points stand out to me in Apple's
documentation:
"exceptions are resource-intensive in Objective-C"
"Conditions giving rise to exceptions are due to programming errors; you shoul
I want to be able to employ a delegate method after a delay. So what I have
done, which works fine, is create a method in my class that calls the delegate
method, and then I use performSelector:withObject:afterDelay: to call the
second method:
[self performSelector:@selector(doSomething00) wit
thanks - obvious. Should have caught this on my own:)
From: Bill Bumgarner
To: Helen Cooper
Cc: cocoa-dev@lists.apple.com
Sent: Wed, December 30, 2009 12:37:38 PM
Subject: Re: Using performSelector:withObject:afterDelay: to call a delegate
method?
On Dec 30
I have defined a color palette I want to access routinely as UIColor objects,
but I am not convinced I am taking the right approach, particularly in regard
to managing memory and minimizing memory used. I have defined a bunch of colors
as follows, and am wondering if there is a better way to do