|
|
Should be a hint on it's own!
This one is really a hint in it's own right... I had no idea that you could access the resource fork that way!
Should be a hint on it's own!
It turns out Rob already has posted a hint about this here, and there's an interested comment at the bottom about using the '..namedfork' route to get at any named fork.
You're right about there being some overhead with a resource fork. When you 'create' a resource fork with ResEdit, it adds a header to the fork. But every file does automatically have a resource fork that you can read from and write to, it just normally has length 0, i.e. no header info. Michael |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.42 seconds |
|