The main issue with the original code is that it assumes that the value is a
CGPoint. If it were anything smaller, you'd get garbage values in your point,
and if it were any larger, you'd be stomping on memory as you ran off the end
of your CGPoint variable.
Any time you use -[NSValue getValue:
Thanks
pointValue didn't work on iPhone OS but CGPointValue did, luckily, as that's
the one I needed. That seems to be a UIKit extension. I've switched to that.
was my original method (apart from being clunky) wrong? It did work.
On 03-Apr-2010, at 10:43 PM, Kiel Gillard wrote:
> On 04/04/2
On 04/04/2010, at 1:40 AM, Roland King wrote:
> I have a property which is a CGPoint and I'm observing it. I didn't really
> know what to expect in the change dictionary (I have NSKeyValueObservingOld
> as the observation flags) so I stuck in a breakpoint and went looking. After
> messing about
