On 10/17/09 10:21 PM, Alastair Houghton said: >On 17 Oct 2009, at 03:12, Sean McBride wrote: > >> On 10/10/09 11:15 AM, Sander Stoks said: >> >>> First, do I really have to add all types to my Info.plist file? If >>> the OS gets an update which adds a new file type to Image I/O, I have >>> to update my Info.plist? >> >> Since no one else replied... I'm pretty sure the answers are: yes >> and yes. :( > >Well, you *could* do a little better than doing it manually; e.g. when >you run the application, it could look at NSImage's -imageTypes method >and see if it had every one of them listed in your Info.plist, then if >there are some that aren't, update your Info.plist accordingly. Of >course, this is trickier than it sounds, because if your app is run by >a non-admin user you're going to have to use a helper tool and >Authorization Services to update the Info.plist.
That's a clever idea, but, as you say, fragile. I believe it would also break code signing, would it not? Still, it could be used in debug builds to detect when new image formats are supported, then at least you'd know its time to release an update. -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
