On Thu, Apr 3, 2008 at 4:31 AM, Daniel Thorpe <[EMAIL PROTECTED]> wrote:
> I have gone with using a ...AsString attribute and using NSRectFromString. > Seems to work okay, although I've got no idea if it's the most efficient > method. I think Core Data seems a little limited in that you can't store an > NSValue object as an attribute, I'd have thought that would be obvious, as > we use that class to store structs in collection objects.... I'm not sure, but I think the $64,000 question is how to handle (a) struct padding and (b) endieness issues. With something like a NSRect it should be easy (write a special case in NSValue) but for arbitrary structs the problem is insurmountable. _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
