Using NSSearchField and remaining Jaguar compatible?
Using NSSearchField and remaining Jaguar compatible?
- Subject: Using NSSearchField and remaining Jaguar compatible?
- From: Michael McCracken <email@hidden>
- Date: Fri, 6 Feb 2004 18:00:51 -0800
Hi, I'm trying to figure out the best design for using NSSearchField
(avail. only in 10.3) and remaining backwards-compatible with Jaguar.
I'm aware that this sounds like a FAQ, but previous posts I've found
have asked about getting arbitrary classes that don't exist in 10.2,
and I'm asking about getting something I've placed in a nib. Pretty
similar, but I thought there might be a different solution in this
case. So:
My idea of best solution is to have a single app that runs on both and
just provides a different UI (just an NSTextField) on Jaguar.
The search field is in a toolbar, so I will have to test availability
macros to be sure the named toolbar item is version appropriate. No
problem there.
The problem (which I posted about earlier, but can't find in the
archives, d'oh) is that my app crashes when trying to decode the nib
that contains the NSSearchField. Right now, the nib with the
NSSearchfield is my NSDocument subclass' main nib.
So, do I need to create a separate nib with the NSSearchField, and load
that separately if I'm in 10.3?
That's not too bad, but I thought my new-format nib would have taken
care of the loading problem for me, so I was wondering if there was
something else going on.
Thanks,
-mike
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.