Re: Working with creator codes in OS X
Re: Working with creator codes in OS X
- Subject: Re: Working with creator codes in OS X
- From: garbanzito <email@hidden>
- Date: Tue, 4 Sep 2001 15:56:03 -0600
At 10:15 +0200 2001 09 03, Axel Luttgens wrote:
Technically, AS doen't allow to "remove" a creator type (this would need a
disk editor or some similar software). But if the intend is to "modify the
behavior of a document's icon upon double clicking", then the question is
somewhat broader and refers to OSX's mechanism of binding document files to
apps.
For example, under some circumstances, it could be sufficient just to change
(or remove) a file's extension.
Or, since type/creator (when defined) seem to have prevalence in OSX's
Finder, to put the signature of another application (or to use some reserved
creator code with a conventional meaning; Garbanzito seems to have pointed
such one).
if the creator doesn't match to any application, the file
name extension will take precedence. so it seems that <four
spaces> or 'msng' would be sufficient to effectively
"remove" the creator, but you're right, that's different
from four nulls. even with ResEdit or
/Developer/Tools/SetFile i couldn't find a way to set a
creator code to null.
By the way: when associating a given document to a given application (in the
Finder's "Info for..." dialog), the information seems to be stored in... the
document's resource fork (OSX 10.0.4).
Is this true, or just a bad interpretation of mine?
yes, i observe the same behavior.
--
steve harley email@hidden