Yes, that's what I do. I call NSClassFromString(@"NSPredicateEditor")
and create one of two classes depending of call's result. Each class
loads its own NIB and this should guarantee me that I never call
unsupported code.
Thanks for the explanation.
On Sun, Jan 18, 2009 at 3:23 PM, Ken Thomases
On Jan 18, 2009, at 4:15 AM, Vitaly Ovchinnikov wrote:
Well, after reading your link one more time, I found this:
http://developer.apple.com/documentation/DeveloperTools/Conceptual/cross_development/Using/chapter_3_section_4.html#/
/apple_ref/doc/uid/20002000-1114537
So, I am right for Tiger
Well, after reading your link one more time, I found this:
http://developer.apple.com/documentation/DeveloperTools/Conceptual/cross_development/Using/chapter_3_section_4.html#//apple_ref/doc/uid/20002000-1114537
So, I am right for Tiger and Leo, that OSX uses lazy loading and if I
never call NSPre
There are many common words, but no answer on my question. The
question is simple: can I include some Leopard-only code that will
never be executed on Tiger? Will Tiger run such app or, like Windows,
it will try to load all referred classes first?
On Sun, Jan 18, 2009 at 11:12 AM, Rob Keniger wro
On 18/01/2009, at 5:50 PM, Vitaly Ovchinnikov wrote:
When I try to compile the code against 10.4 SDK - I receive a lot of
errors because there is no NSPredicateEditor on Tiger. I switched
target platform version to 10.5 and now it compiles and links without
a problem. I also set Deployment Targ
Hello list,
I need to use NSPredicateEditor class in my app that should work both
on Tiger and Leopard. But Tiger doesn't have such control, so I
created two different NIBs and load one of them depending on current
platform. Each NIB has it's own owner-class that implements some
logic. Owner of NI
