• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSAppKitVersionNumber for 10.3.0?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSAppKitVersionNumber for 10.3.0?


  • Subject: Re: NSAppKitVersionNumber for 10.3.0?
  • From: Chuck Soper <email@hidden>
  • Date: Tue, 21 Sep 2004 10:13:46 -0700

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.
Chuck


At 3:25 PM -0300 9/20/04, Rainer Brockerhoff wrote:
At 08:19 -0400 20/09/2004, Jim Correia wrote:
On Sep 20, 2004, at 7:15 AM, Rainer Brockerhoff wrote:

AFAIK 10.1.x ignores LSMinimumSystemVersion, 10.2.x quits with a message, and 10.3.x quits without a message. So to be safe I write:

[...]

...with the added bonus that you can write your own apologetic/snippy/obscure message ;-)

The downside to this approach is that if your app requires 10.3, you are plain out of luck on 10.1, and you have to make sure you weak link so that the app can close and come up on 10.2 to just tell people that the app won't run there.

Yes, I took for granted that my solution requires weak-linking against "new" APIs, which is a hassle. I suppose with "plain out of luck on 10.1" you mean the two-level linking problem? I admit I no longer have access to any Mac with 10.1.x installed to check this out.


Of course, one easy way out is to have a small version-checking executable that runs your main executable only if the version is correct...


-- Rainer Brockerhoff <email@hidden> Belo Horizonte, Brazil

_______________________________________________ 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
  • Follow-Ups:
    • Re: NSAppKitVersionNumber for 10.3.0?
      • From: Finlay Dobbie <email@hidden>
    • Re: NSAppKitVersionNumber for 10.3.0?
      • From: Frederick Cheung <email@hidden>
References: 
 >Re: NSAppKitVersionNumber for 10.3.0? (From: Rainer Brockerhoff <email@hidden>)
 >Re: NSAppKitVersionNumber for 10.3.0? (From: Jim Correia <email@hidden>)
 >Re: NSAppKitVersionNumber for 10.3.0? (From: Rainer Brockerhoff <email@hidden>)

  • Prev by Date: Re: User Picture
  • Next by Date: Re: NSAppKitVersionNumber for 10.3.0?
  • Previous by thread: Re: NSAppKitVersionNumber for 10.3.0?
  • Next by thread: Re: NSAppKitVersionNumber for 10.3.0?
  • Index(es):
    • Date
    • Thread