Issues with plug-in loading within Quesa.

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

Hi Quesa list,

We have have come across a problem in Quesa while testing. The problem 
involves having an application ( using Quesa ) running from an AFP(OSX 
10.3) users desktop with an alias to a SMB share.

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 it really be doing this a application bundle 
level on OSX.

I have listed the code section I feel should be changed or removed 
below. The other option is to have better alias resolve code.

File:
E3MacSystem.cp

Function:
void
E3MacSystem_LoadPlugins(void)

Code Section:
	// Find the application file
	if (isOnOSX)
		{
		theErr = GetProcessBundleLocation( &thePSN, &bundleFSRef );
		
		if (theErr == noErr)
			{
			theErr = FSGetCatalogInfo( &bundleFSRef, 0, NULL, NULL, &fileSpec[ 
dirCount ], NULL );
			}
		}
	else
		{
		processInfo.processInfoLength = sizeof(ProcessInfoRec);
		processInfo.processName       = NULL;
		processInfo.processAppSpec    = &fileSpec[ dirCount ];
		
		theErr = GetProcessInformation(&thePSN, &processInfo);
		}
	
	if (theErr == noErr)
		++dirCount;

Code Line problem:
	if (isOnOSX)
		{
		theErr = GetProcessBundleLocation( &thePSN, &bundleFSRef );
		
		if (theErr == noErr)
			{
			theErr = FSGetCatalogInfo( &bundleFSRef, 0, NULL, NULL, &fileSpec[ 
dirCount ], NULL );
			}
		}



What would other people suggest.

Peter Michelsen