On Mar 10, 2012, at 23:18 , Eric Wing wrote:
> I don't disagree that finalizers are hard and need to be approached
> with great care. And I agree that all 4 of your points are valid.
> However, I think this description of the retain cycle problem might be
> a little over-dramatic. Retain cycles ha
Yes.
+initialize is not call until you try to use your class.
So there is no garantee it will be call at all, and even if it is called,
nothing prevent creation of instance of the super class before it append.
Le 11 mars 2012 à 08:05, Antonio Nunes a écrit :
> In the latest public release of my
On 11 Mar 2012, at 09:48, Jean-Daniel Dupas wrote:
> +initialize is not call until you try to use your class.
> So there is no garantee it will be call at all,
Thanks Jean-Daniel,
I think I can be pretty confident it is called, since this initialize is in my
NSApplication subclass. Should be ca
On 11 Mar 2012, at 08:01, Quincey Morris wrote:
> On Mar 10, 2012, at 23:18 , Eric Wing wrote:
>
>> I don't disagree that finalizers are hard and need to be approached
>> with great care. And I agree that all 4 of your points are valid.
>> However, I think this description of the retain cycle pro
Le 11 mars 2012 à 13:28, Antonio Nunes a écrit :
> On 11 Mar 2012, at 09:48, Jean-Daniel Dupas wrote:
>
>> +initialize is not call until you try to use your class.
>> So there is no garantee it will be call at all,
>
> Thanks Jean-Daniel,
>
> I think I can be pretty confident it is called, sin
Hello,
in a custom view I'm processing -scrollWheel: events for smooth
scrolling using the trackpad.
When the user flicks across the trackpad, scrolling events first go
through a phase cycle delivered through [NSEvent phase]
(NSEventPhaseBegan -> NSEventPhaseChanged -> NSEventPhaseEnded).
