On Dec 14, 2010, at 9:01 AM, Matt Neuburg wrote:
>
> Doesn't anyone besides me want to evince any outrage that this can happen? I
> mean, sheesh, if I wanted to live in a world where the namespace was polluted
> with secret undocumented terminology I could collide with accidentally, I
> could
>>Hmm, also, it appears that UIResponder has some undocumented methods
>>-firstResponder and -_firstResponder, which your synthesized property would
>>also interfere with.
>
> Doubtless. But how would I have discovered this?
I would have implemented -firstResponder and set a breakpoint to see
wh
On Dec 14, 2010, at 10:01 AM, Keary Suska wrote:
> On Dec 13, 2010, at 12:01 PM, Matt Neuburg wrote:
>
>> self->firstResponder = tf;
>
> Well, the proper syntax is self.firstResponder . Using the deference is
> probably a back-door way to access the class struct. Unless I misunderstand
> so
On Dec 14, 2010, at 10:01 AM, Keary Suska wrote:
> On Dec 13, 2010, at 12:01 PM, Matt Neuburg wrote:
>
>> self->firstResponder = tf;
>
> Well, the proper syntax is self.firstResponder . Using the deference is
> probably a back-door way to access the class struct. Unless I misunderstand
> som
On Dec 13, 2010, at 12:01 PM, Matt Neuburg wrote:
>self->firstResponder = tf;
Well, the proper syntax is self.firstResponder . Using the deference is
probably a back-door way to access the class struct. Unless I misunderstand
something
Keary Suska
Esoteritech, Inc.
"Demystifying techno
On Mon, 13 Dec 2010 11:31:38 -0800, Wim Lewis said:
>
>On 13 Dec 2010, at 11:01 AM, Matt Neuburg wrote:
>> How can this seemingly minor change make such a big difference? I'm not even
>> *using* the synthesized accessor! Yet its mere presence breaks the project.
>> How can this be? m.
>>
>> PS
On Dec 13, 2010, at 1:31 PM, Wim Lewis wrote:
>
> On 13 Dec 2010, at 11:01 AM, Matt Neuburg wrote:
>> How can this seemingly minor change make such a big difference? I'm not even
>> *using* the synthesized accessor! Yet its mere presence breaks the project.
>> How can this be? m.
>>
>> PS A n
On 13 Dec 2010, at 11:01 AM, Matt Neuburg wrote:
> How can this seemingly minor change make such a big difference? I'm not even
> *using* the synthesized accessor! Yet its mere presence breaks the project.
> How can this be? m.
>
> PS A new discovery: changing the name of the ivar / property to
I have reduced this problem (after losing an entire day of work, of course) to
a very few lines of code. They won't make much sense but just bear with me.
Here we go...
I have this code (iOS), and it works fine:
@interface TextFieldFunViewController : UIViewController {
UIView* firstRespond
