At 7:43 AM -0500 3/15/06, Thom McGrath wrote:
Not true. Apple is trying to steer clear of Type and Creator codes, but can't drop them as easily as they did resource forks. On OS X, I call it a bug that RB does not recognize a ".tif" file as matching the FileType.
It does, if the file whose name ends with ".tif" doesn't have a type or creator. This is correct behavior. It would be a bug if it allowed a properly typed file to be matched by its name, or if it failed to match untyped files by their name.
I mean, what are the extensions for anyways?
For making the folks who previously worked at NeXT feel good about themselves. Also for making it easier to transfer files to/from more primitive operating systems.
As well, RB really gets confused when you are designing a bundle-type document format, because it's impossible to have a type code assigned!
No, untyped files are matched just fine by extension. There may be a bug with support of bundle documents, but that would be a completely separate issue.
Best, - Joe -- Joseph J. Strout [EMAIL PROTECTED] _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
