Re: Issues with plug-in loading within Quesa.

[Peter M. <Pet...@mi...>]

Sorry, I will try to make it a bit more clear.

> What is a specific example of a case where a plugin does not get 
> loaded when it should?

The problem is not with loading a plug-in but in the way in which it is 
looking for plug-ins to load.

>> theErr = GetProcessBundleLocation( &thePSN, &bundleFSRef );

This line above returns a link to where the application is stored e.g. 
" /private/Network/Servers/jupiter/Users/jbatt/Desktop/3D\ World.d.app 
" Later the function  " e3mac_load_plugins( &fileSpec[i] ); " is called 
which calls " theErr = ResolveAlias(NULL, gQuesaLib, &fileSpec[ 
dirCount ], &wasChanged); " This fails causing Quesa to assert.

The problem
>> While Quesa is loading it tries to look for plug-ins (GOOD), while it 
>> is looking for  plug-ins Quesa tries to resolve any alias (FINE most 
>> of the time), but should Quesa really be doing this at application 
>> bundle level on OSX.

Now the solution to the problem is either, that Quesa should not search 
outside of the application bundle it is in, for plug-ins.

Or that "ResolveAlias" should have checking code before it is called. 
What checking code I do not know?

Peter Michelsen