Re: Issues with plug-in loading within Quesa.

[James W. W. <ja...@wr...>]

Sorry, lost the quoting on that post, let's try again:


Peter Michelsen <Pet...@mi...> wrote:

>  Yes you are right the function call is... 
>ResolveAliasFile(&theFSSpec, true, &targetIsFolder, &wasAliased); I 
>had copied the wrong call.

But, what exactly goes wrong with this call?  Does it show an alert 
requesting that a volume be mounted, or what?

>But luckily this did force me to look in developer.apple.com for 
>this function. They have list the call as        Not recommended

I think that's just because it uses an FSSpec.  I would not be 
opposed to switching to FSRefs, but I don't think we've made an 
official decision to drop support for Mac OS 8.

>  I also noticed that there is a call the FSResolveAliasFilewithMountFlags.

If what you need to do is avoid UI, there is an FSSpec-compatible 
function ResolveAliasFileWithMountFlags.

As I look at this code, I think I see another problem:  If the file 
was an alias, we should get the file type and creator of the actual 
file, not the alias.  The type and creator are probably correct for a 
normal alias, but not for a symbolic link.

As long as we're discussing plugin loading, does anyone know whether 
the current system works when Quesa is built as a Mach-o framework, 
or do we need to add some sort of Mach-O-CFM glue?
-- 
   James W. Walker, ScriptPerfection Enterprises, Inc.
   <http://www.write-brain.com/>