Re: IB is listing non-outlets as outlets
Re: IB is listing non-outlets as outlets
- Subject: Re: IB is listing non-outlets as outlets
- From: j o a r <email@hidden>
- Date: Sat, 19 Mar 2005 01:31:41 +0100
IB rather recently got support for IBOutlet and typed outlets. Prior to
that all outlets were of the type "id". Supporting "id" after the
addition of typed outlets is probably done for backwards compatibility.
You can find some info on this in the IB release notes.
j o a r
On 2005-03-19, at 00.09, Ricky Sharp wrote:
This is probably a bug in IB, but thought I'd post here first.
For my custom palette items (mostly subclasses of NSControl), I offer
custom bindings. For a particular binding, the control subclass has a
pair of private ivars. For example:
@interface MyControl : NSControl
{
@private
id observedObjectForFoo;
NSString* observedKeyPathForFoo;
}
In IB, when I control drag from such a control (e.g. to connect up
delegates, next key view, etc.), I'm seeing a list of these private id
ivars as if they were declared as being outlets. In the example
above, 'observedObjectForFoo' would show up in the list of outlets I
could connect to.
It's not a huge deal as I'm the only one that will ever use these
palette items and I know not to connect such things. Still, it does
clutter the list of outlets especially for those controls that offer
several custom bindings.
Anyone know why IB is doing this?
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden