Re: Deciphering an error message on an iOS UITextField subclass.

2018-01-18 Thread Saagar Jha
So, I don’t see you trying [cell.dataField property] in your log below. Does this work? Saagar Jha > On Jan 17, 2018, at 20:27, Alex Zavatone wrote: > > >> On Jan 17, 2018, at 9:28 PM, Saagar Jha > > wrote: >> >> >> Saagar Jha >> >>> On Jan 17, 2018, at 18:52,

Re: Deciphering an error message on an iOS UITextField subclass.

2018-01-17 Thread Alex Zavatone
> On Jan 17, 2018, at 8:07 PM, Quincey Morris > wrote: > > On Jan 17, 2018, at 17:58 , Alex Zavatone > wrote: >> >> Cell does not have this problem and is the proper subclass. It properly >> reports both its class and the expected result for if it is a kind of >> UITabl

Re: Deciphering an error message on an iOS UITextField subclass.

2018-01-17 Thread Saagar Jha
If you’re being lazy, just use the selector for the getter: [cell.dataField property]. It might not perform checking, but it will work if the selector is defined. Saagar Jha > On Jan 17, 2018, at 17:24, Alex Zavatone wrote: > > Xcode 9.2, iOS 11.2 > > In a UITableViewCell subclass, I have a

Re: Deciphering an error message on an iOS UITextField subclass.

2018-01-17 Thread Steve Christensen
> On Jan 17, 2018, at 5:24 PM, Alex Zavatone wrote: > > po [cell.dataField isKindOfClass:[UITextField class]] Have you tried "print [cell.dataField isKindOfClass:[UITextField class]]", instead, possibly casting the result to bool? The debugger may be getting confused when you're asking it to

Re: Deciphering an error message on an iOS UITextField subclass.

2018-01-17 Thread Quincey Morris
On Jan 17, 2018, at 17:58 , Alex Zavatone wrote: > > Cell does not have this problem and is the proper subclass. It properly > reports both its class and the expected result for if it is a kind of > UITableViewCell class. What the debugger is telling you is from run-time examination of the cla

Re: Deciphering an error message on an iOS UITextField subclass.

2018-01-17 Thread Quincey Morris
On Jan 17, 2018, at 17:24 , Alex Zavatone wrote: > > Am I right in assuming that Xcode thinks that the subclass has 2 possible > UITextField parent classes? Well, the error message about ambiguity is confusing enough that it’s worth a bug report (even if it’s only a minor problem). What is th