Right. My question was framed improperly I guess. If you were just trying to recover data in old Mac files, then one would only need to READ the resources, but you were talking about *writing*resources, and I was curious why one would want to sustain a discontinued (and broken) technology in a new application.
No big deal. Inquiring minds... etc. On 30 May 2010 13:19, Mark Schonewille <[email protected]>wrote: > Stephen, > > I'm dealing with files that contain resource forks, not with stacks. > > > -- > Best regards, > > Mark Schonewille > > Economy-x-Talk Consulting and Software Engineering > Homepage: http://economy-x-talk.com > Twitter: http://twitter.com/xtalkprogrammer > > Economy-x-Talk is always looking for new projects. Contact me for a quote > http://economy-x-talk.com/contact.html > Download Clipboard Link http://clipboardlink.economy-x-talk.com and share > the clipboard of your computer over the local network. > > On 30 mei 2010, at 21:52, stephen barncard wrote: > > How odd. I remember using the Rev resource calls to try and recover and >> convert some audio resources in old stack. I think I ended up using >> SoundEdit to recover the audio resources, so it must have not been >> successful in rev. >> >> I noticed you want to write as well as read resources. May I ask why you >> want to even use this unsupported technology today, and why your problem >> can't be accomplished with custom properties? >> >> sqb >> > > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > -- ------------------------- Stephen Barncard San Francisco _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
