Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: launch services file association

Larry,
 
Yes, I'm a newbie.  I've got about 10 mac books at home, and am doing my best to learn about this stuff. 
 
As far as being stuck, the only thing that's curious is why I can do what I need through the defaults program but not programmatically.  It sure seems like your original suggestion about <key>LSIsAppleDefaultForType</key> should have worked.  I wonder what that key is for, anyway?  It doesn't seem to do anything.
 
I'll try the DTS folks.  Thanks a lot again.
 
--Daniel
 
> > > Also:
> > > <key>CFBundleTypeOSTypes</key>
> > > <array>
> > > <string>dart</string>
> > > </array>
> > >
> > > All FourCharCodes that are all lowercase (such as this file type)
> > are
> > > reserved by Apple, so you should have at least one upper case letter
> > > in your file type. (Using all lowercase like this is just setting
> > > yourself up for another potential conflict with an Apple
> > > application.) Do the files that are opening in the wrong application
> > > have this file type?
> > >
> > > Larry
> > >
> >
> > Yes. I believe I understand file type correctly here to mean the
> > file extension: "*.dart".
>
> With all due respect, it would probably behoove you to understand the
> basics of the Mac before writing applications for it. Based on some
> of your posts, I sense that you have little or no experience as a Mac
> developer. No, the term "file type" does not refer to the file
> extension. One would think that's obvious since there are separate
> keys for CFBundleTypeOSTypes and CFBundleTypeExtensions in your
> property list.
>
> The Mac has always supported the use of a four-byte creator to bind a
> file to an application, and another four-byte value (file type) to
> specify a file's type. Prior to Mac OS X, the file extension was
> simply part of a file's name and had no special meaning. Since the
> rest of the world is determined to think that the confusion such a
> system avoids has little or no value, Mac OS X supports file
> extensions so we on the Mac side can now deal with the same stupid
> extension conflict issues you folks have had to endure on other
> platforms for years. Fortunately, Mac OS X supports extensions of
> arbitrary length so that when we define one we can make it long
> enough that an extension conflict is highly unlikely.
>
> > As I pointed out in a response about using Creator, the problem
> > here is that files will often arrive copied from another OS or phone,
>
> I had assumed that, which is why I didn't suggest relying on the
> creator, but file types would suffer from the same limitation.
>
> > so I don't have control over the extension, which already exists,
> > or the case. But would using "*.Dart" really fix it? I thought
> > these filenames were case insensitive....
>
> See above.
>
> The upshot of all this is that I think you're probably stuck unless
> someone else or DTS has a better answer for you.
>
> Larry
>


View Athletes' Collections with Live Search. See it! 
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden

This email sent to email@hidden


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.