Re: Subclassing a view class from an external framework
Re: Subclassing a view class from an external framework
- Subject: Re: Subclassing a view class from an external framework
- From: Mark Gallegly <email@hidden>
- Date: Thu, 15 Oct 2009 16:34:57 -0700
- Thread-topic: Subclassing a view class from an external framework
Turns out the issue I was having was caused by the fact that I did not have
the headers in the framework bundle, once I figured out how to add the
header files to the framework - which was not easy to figure out - and did
the 'reload all class files' menu item in IB for each xib the problem went
away. At least on my xcode 3.2.1 machine. On a machine running xcode 3.1 the
warnings still show up, but I have not bothered to open each xib and choose
to 'reload all class files' yet..
Mark
On 10/15/09 4:24 PM, "Kevin Cathey" <email@hidden> wrote:
>> Although Interface Builder 3 is supposed to automatically sync with header
>> files in your project, it seems to have trouble with headers in frameworks.
> Which version of Interface Builder were you seeing this on? IB 3.2.x will
> parse the headers for all frameworks you've linked against in your Xcode
> project.
>
> Kevin
>
> On 13 Oct 2009, at 07:55, Jeff Johnson wrote:
>
>> Hi Mark.
>>
>> I had the same problem with NSWindow subclasses. Although Interface Builder 3
>> is supposed to automatically sync with header files in your project, it seems
>> to have trouble with headers in frameworks. What I did was select "Read Class
>> Files..." in the "File" menu of Interface Builder and read the header file
>> for my framework class. The solved the problem for me.
>>
>> -Jeff
>>
>>
>> On Oct 12, 2009, at 11:22 AM, Mark Gallegly wrote:
>>
>>> I have an NSView subclass defined in a framework called FrameworkView. The
>>> FrameworkView class has a property like so:
>>>
>>> @property (nonatomic, retain) IBOutlet NSView* someView;
>>>
>>> This framework has the necessary code in it to work as an Interface Builder
>>> plugin, and everything seems to work fine in Interface Builder.
>>>
>>>
>>> However, if I subclass the FrameworkView in a separate project that contains
>>> my .app target, with say a class called MyFrameworkViewSubclass, I get a
>>> warning like this when building the .xib file containing
>>> MyFrameworkViewSubclass:
>>>
>>> The 'someView' outlet of 'MyFrameworkViewSubclass' is connected to 'Custom
>>> View' but 'someView' is no longer defined on MyFrameworkViewSubclass.
>>>
>>> Now, within IB the outlet shows up and I am able to make the connection, and
>>> when the app runs everything works fine, but for some reason XCode spits out
>>> this warning. Does anybody know what is going on here and how to get rid of
>>> the warning?
>>
>> _______________________________________________
>>
>> Cocoa-dev mailing list (email@hidden)
>>
>> 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:
>>
>> This email sent to email@hidden
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden