At 0:30 +0100 8/14/98, Jay Bedsole wrote: >I wonder why Apple doesn't store this as text in the data fork? >I have a theory - Apple thought it was such a swell concept, >they wanted to insure users used it as much as possible... after >all, once you create a text clipping file, the only way to use >it was to drop it back onto the content of an application >document... you can't drop it onto your favorite text or word >processor like an ordinary text document... Not at all. While a data fork with identified multiple flavors of data could have been designed, why? The files aren't cross platform anyhow, and the resource fork does small quantities of typed data very well. And, the data passed by the drag manager begs to be treated this way. Remember, you can have text, related styles (in "styled text" form), PICT, sound, etc all in one clipping file if you can arrange to make it happen (the app from which the thing is dragged to Finder does the arranging, and the Frontier code I mentioned before is happy to do it for you, also). Code shouldn't assume that there is just a TEXT resource and that it is ID 256...there's an indexing resource which indicates the flavors and resource IDs (Finder always creates with ID 256...at least so far). Maybe someday I'll have time to write some code again...the format is quite simple. Sigh! --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA Give a man a fish and you feed him for a day. Teach him to fish, and you get rid of him for the weekend. ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch