Ken, I understand that the resource fork thing was very MacClassic oriented. Still, one wonders why there isn't a ca 1987 elegant, modern solution in 2003.
Yes, there are many different ways of doing one thing; problem is, it doesn't matter if they're all equally inelegant/non-intuitive. Maybe it's the non-assembly code programmer in me, but it's just not clear why, once you've embedded something, you have to re-embed it with each usage. This is just nuts. This results in bloatware. Sorry -- not a personal attack. Really. Judy On Mon, 3 Feb 2003, Ken Ray wrote: > Judy, > > In a cross-platform world, there aren't resource forks on both sides of the > fence, unfortunately, so we need to make do. Now the inelegant solution is > only true if you want the images *embedded* into the stacks; if you don't, > you can leave them on disk and reference them as many times as you like from > wherever you like. _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
