Re: Unknown class ‘MyCustomView', using 'NSView' instead
Re: Unknown class ‘MyCustomView', using 'NSView' instead
- Subject: Re: Unknown class ‘MyCustomView', using 'NSView' instead
- From: Erwin Namal <email@hidden>
- Date: Mon, 23 Feb 2015 08:26:30 +0100
Thank you for your replies. I wish to avoid the framework, so all the code is statically linked and I don’t bother with framework installation. It not very efficient, but the compiled library does not take a lot of disk space, so it is easier this way.
About the app behaving the same, I wrote too quickly. Functions implemented in the view are not used very often. And I first check if the instance of NSView responds to the selector before sending the message so I don’t see the bug right away….
Where should I put the linkerhack class? (library or app ?)
>> On 22 Feb 2015, at 19:17, Erwin Namal <email@hidden> wrote:
>>
>> Thank you for your reply.
>> I already use both Other linker flags “-ObjC” and “-all_load” in the library, in its bundle target (though it is useless I think) and in the application including the library and the bundle with the nib.
>> Then, I load the nib in the bundle by using :
>>
>>> initWithNibName:nibName bundle:libraryBundle
>>
>> The other linker flags did solve the issue of categories in the library not visible in the application.
>> The thing I don’t understand is that I get the warning, but my application works fine. It shouldn’t if NSView was indeed used instead of MyCustomView.
>>
>> Where do you put your linkerhack class ? In the library or in the app ?
>>
>> Thanks for your help
>> – E
>>
_______________________________________________
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