Re: iPhoto returns a real number as a photo ID
Re: iPhoto returns a real number as a photo ID
- Subject: Re: iPhoto returns a real number as a photo ID
- From: Rob Lewis <email@hidden>
- Date: Wed, 16 Jun 2010 09:04:58 -0700
Aaargh. I'm tempted to say forget the whole thing, especially after being informed that you can't even depend on a photo's "id" property to remain the same from one run to the next. What's the point then? How great it would be if iPhoto/AppleScript would simply use the industry-standard Exif tag, ImageUniqueID.
I'm increasingly frustrated and dismayed by the lame and inconsistent ways that Apple's apps handle (or fail to handle) metadata. Another example: a user can spend a lot of time adding metadata tags to an image file. Then import the file into iPhoto and make any edit (crop, rotate, etc.). This will result in the creation of a "Modified" copy of the file with--surprise!--much of the laboriously applied metadata simply gone. Email a photo to a friend: metadata gone.
Apple is a member of the Metadata Working Group ( metadataworkinggroup.org) yet it doesn't follow the group's recommendations. And sadly, the group has apparently left loopholes in the spec to allow some of this bad behavior to continue--at the expense of users and third parties. (I know Apple isn't the only guilty party, but trying to use AppleScript and metadata is a recipe for frustration.)
</rant>
To be clear: the indications are that iPhoto is handing back 32-bit
integers, not 64-bit ones. The coercion to floating point done by
AppleScript in that case doesn't lose any information. I only meant
to answer Shane's question about how coercion to floating point could
lose data; apologies for the FUD.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden