Kyle, Yes, AATappableLabel.m is indeed a member of the target. (I checked it multiple times.) Moreover, I have confirmation of this in other places in the application, where I use the AATappableLabel class directly embedded in a UIView (rather than in the contentView of a UITableViewCell) and it behaves as expected there.
That’s one of the things that has me mystified about what I am seeing here. I know that cross-posting is usually bad form, but in this case I am truly unsure whether this is an Xcode problem (i.e., something relating to the compilation of the storyboard) or a Cocoa problem (i.e., a problem with the instantiation of the object. Please accept my apology. Cheers, Rick Aurbach On Feb 13, 2014, at 6:23 PM, Kyle Sluder <[email protected]> wrote: > On Thu, Feb 13, 2014, at 01:53 PM, Rick Aurbach wrote: >> Notice that the storyboard recognizes that the label ought to instantiate >> a custom class (see red text above), but that doesn’t happen >> >> * if I set breakpoints in the initxxx methods, they are never hit >> * if I break in the method where the cell is instantiated, the >> debugger identifies the object as a UILabel, rather than an >> AATappableLabel. > > Is AATappableLabel.m a member of your target? If not, the nib loader > will fall back to UILabel. > > --Kyle Sluder _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
