I stand corrected; I've seen this many times before, and have never had
problems. I'm guessing it's one of those patterns that causes problems under
specific circumstances?
Cheers,
Adam
On Fri, Jan 9, 2009 at 7:40 PM, Kyle Sluder wrote:
> On Fri, Jan 9, 2009 at 7:11 PM, A
I've noticed a pattern in some Apple code where the instance variables are
all prefixed with an underscore, but the property name, and therefore the
accessors, are what you'd expect. This leaves you free to use the same name
for arguments. To make the property point to the right variable, use an =
Hi Stuart,
I'm still something of a neophyte, but a theme I've found in threads here is
that consistent use of accessors tends to save memory management headaches
if you're not using garbage collection. If you use @property and @synthesize
to generate your accessors, and then use them to both init
ed
to keep reading so I can make it look halfway decent :)
Thanks again to everyone who chimed in.
Cheers,
Adam
On Tue, Jan 6, 2009 at 10:31 AM, Adam Foltzer wrote:
> To the list this time :D
>
>
> -- Forwarded message ------
> From: Adam Foltzer
> Date: Tue,
To the list this time :D
-- Forwarded message --
From: Adam Foltzer
Date: Tue, Jan 6, 2009 at 10:00 AM
Subject: Re: Visualization strategy/choosing a framework
To: Andrew Farmer
I found the Accelerate framework after posting this, and have had some good
success with it on my
is isn't my area of expertise, but I just have one point to make:
>
> On Dec 31, 2008, at 9:19 PM, Adam Foltzer wrote:
>
> I also see Quartz mentioned as a friendlier wrapper for OpenGL, but again
>> I
>> get the impression that it's more geared toward 2-D rendering tha
Thanks very much for your input, everyone. This seems to be the key theme:
On Thu, Jan 1, 2009 at 3:48 AM, Andrew Farmer wrote:
> It isn't. Quartz is a 2D graphics library and has no 3D capabilities - if
> what you're after is 3D rendering of any variety, go directly to OpenGL; do
> not pass GO;
Hello everyone,
I've been lurking here for a while as I've been learning the Cocoa ropes,
and I'm at the point where I need to put the (excellent) Hillegass theory
into practice. My app is an interactive particle swarm optimization (
http://en.wikipedia.org/wiki/Particle_swarm_optimization for the
