On Friday, April 26, 2002, at 12:44 PM, David W. Fenton wrote:
> I still do not know for certain if the OS (Mac OS or OS X) has
> system variables for the Application and Documents folders, or
> if they are hard-wired into the system (and created with those
> names and those names only).
The standard calls are FindFolder(), FindFolderExtended(),
FindFolderEx(), FSFindFolder(), and FSFindFolderExtended().
The most often call used by far is FindFolder().
FindFolder(
short vRefNum,
OSType folderType,
Boolean createFolder,
short *foundVRefNum,
long *foundDirID
);
Typical usage of the first two parameters is to supply symbolic
constants to indicate the search path and folder type. There are
too many to illustrate here but for the items in question they
are:
Suitable for 'vRefNum':
kOnSystemDisk
kOnAppropriateDisk
kSystemDomain
kLocalDomain
kNetworkDomain
kUserDomain
kClassicDomain
Suitable for 'folderType':
...
kApplicationsFolderType
kDocumentsFolderType
kVolumeRootFolderType
kChewableItemsFolderType
...
With one exception the system folder names are localized (i.e.
not hard-wired names). As you see by the function parameters,
it's completely up to the caller as to whether or not she would
like to create the folder (which will then be created in the
OS-designated place in the folder hierarchies).
The single exception, as previously discussed in this thread is
the "Applications (MacOS 9)" item which only appeared recently
in MacOS 9 systems which may be coordinated with an OS X
install. I'm currently monitoring 4 Apple Developer lists and
have seen Apple thoroughly blasted for this anomaly (and an
admission of guilt). I've also seen Adobe developers jumped on
for their installer behaviors.
Philip Aker
http://www.aker.ca
_______________________________________________
Finale mailing list
[EMAIL PROTECTED]
http://mail.shsu.edu/mailman/listinfo/finale
