Re: NSAppKitVersionNumber for 10.3.0?
Re: NSAppKitVersionNumber for 10.3.0?
- Subject: Re: NSAppKitVersionNumber for 10.3.0?
- From: Shaun Wexler <email@hidden>
- Date: Tue, 21 Sep 2004 14:03:22 -0700
On Sep 21, 2004, at 10:21 AM, Frederick Cheung wrote:
On 21 Sep 2004, at 19:13, Chuck Soper wrote:
Will simply checking NSAppKitVersionNumber from awakeFromNib in my
NSApp delegate be sufficient? Can I launch a 10.3 or 10.2 app on
10.1.x, get to init or awakeFromNib to check NSAppKitVersionNumber
(before any incompatible APIs are called), and if necessary, call
NSRunCriticalAlertPanel then exit gracefully?
I'm pretty sure there's a reason, but I'm not understanding why weak
linking or installing a small version-checking executable within a
bundle is necessary to determine the version. I need to get this code
properly working in my application. Thanks.
If you have weak linked the appropriate symbols then that is enough.
At launch time the dynamic linker tries to resolve all symbols your
app uses and if it finds a non weak linked symbol that your app uses
it bails out
I posted a demo "Panther-only" application last year, which might be
relevant:
On Nov 22, 2003, at 9:22 AM, Shaun Wexler wrote:
I've received some messages about users unable to get my application
subclassing method to work, where a Panther-only application is able
to launch on pre-10.3 systems and successfully put up a warning
dialog, rather than crashing unmercifully. Here is a sample Xcode
project that illustrates the technique:
http://www.skwdev.com/downloads/SKWTest.dmg
Try launching the app on 10.2 or earlier, to see how it works. Feel
free to use the source in any way.
HTH~
--
Shaun Wexler
MacFOH
http://www.macfoh.com
_______________________________________________
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