On Tue, Jun 3, 2008 at 11:03 PM, Michael Ash <[EMAIL PROTECTED]> wrote: > Note that silently upgrading files when opening is the last thing > you'd want in this case. A file saved using FooApp 1.2 on 10.6 should > still work in FooApp 1.2 on 10.5. If you destroy my files so that they > no longer work on 10.5 without even asking me then I'll get upset.
I actually think this happens when you recompile your app for Leopard and your MOM has non-Tiger-compatible indexes. And if it doesn't, it could, as it would not break backwards compatibility. --Kyle Sluder _______________________________________________ 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 [EMAIL PROTECTED]
