Re: Classic Resource Problem

FROM : John Stiles
DATE : Mon Apr 18 20:49:06 2005

I have used NDAlias with great results, but admittedly I haven't 
tried too much with Classic.
If you're using normal Alias Manager calls, it's quite possible that 
you've found a bug; reduce it down to sample code and file it in 
Radar. I can imagine that the Apple devs probably don't do hardcore 
testing against OS 9.x :)
http://homepage.mac.com/nathan_day/pages/source.html


On Apr 18, 2005, at 11:47 AM, Matt Mashyna wrote:

> I know this seems crazy but...
>
> I have and application that create "droplets". That is, small 
> carbon bundled applications you drop files onto. The way it works 
> is I have a template application as a resource in my Cocoa app. I 
> get different behaviors from the droplets by settings in a plist in 
> their bundles. The scheme works great except that when I create a 
> new droplet, the alias at the root level of the bundle is empty. 
> Seems like my resource forks don't survive the NSWrapper copy 
> NSDocument does. The droplets work for OS X but they need the alias 
> to the executable in the MacOSClassic folder to work.
>
> I tried quite a few tricks to make an alias file or copy one. When 
> I do, the alias looks OK but the droplet will not launch in Classic 
> or OS 9. When I do "Get Info" from the Finder the original file 
> path looks good but the Memory settings are clearly not right. This 
> tells me that I don't have a good alias. The cabon app that is the 
> source for my template has a good alias and does launch in OS 9 and 
> Classic.
>
> It seems like this should be so easy but it's not. I'm wondering if 
> there could be some Finder Flags that need to be set or some other 
> voodoo. Any ideas would really be appreciated.
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Cocoa-dev mailing list      (<email_removed>)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/jstiles%
> 40blizzard.com
>
> This email sent to <email_removed>
>