I don't know if Joanna was suggesting you couldn't make anything available to IB by making it an IBOutlet, I took it that she was saying the old 'compatibility mode' of having any variable of type 'id', even if not an IBOutlet, be visible in IB would not be broken if you restricted it to those variables of type id which were not @private, because @private post-dates any code which should be depending on that old hack.
I sort of agree, but I also sort of don't have this issue, never had a variable of type id in my class. If I did, I'd probably make it NSObject* and .. does that make it stop? On 13-Mar-2010, at 8:04 PM, Alexander Spohr wrote: > > Am 13.03.2010 um 10:32 schrieb Joanna Carter: > >> All that is needed is to detect whether the ivar is @private and to respect >> that visibility. If an ivar is private, it should not be visible in the IB >> designer, regardless of whether it is of type id or not. > > I’d say no to this. > > If my class is files owner the whole nib is owned by it - hence the name. > Therefore I absolutely want IB to be able to set even the private ivars. The > nib is just another way of setting up my class’ objects. > > atze > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > http://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org > > This email sent to r...@rols.org _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
