> > Can you point to any official documentation for the Finder comment xattr > name? > No, I cannot, beyond a support article which relies on the fact ( http://support.apple.com/kb/TA25203?viewlocale=en_US).
I don't really want to be sending apple events to the finder since this is > a background app, and it could be calling it fairly frequently, and I > believe this can impact the user's foreground use of Finder. > You might want to try using AppleEvents as suggested to see if it addresses the original issue and to find out whether their use causes a performance problem or not. However, a background app without a connection to the UI server cannot use high-level events, anyway, since it does not have a process serial number. —Jeremy On Wed, Apr 22, 2009 at 12:09 AM, Adam R. Maxwell <amaxw...@mac.com> wrote: > > On Apr 21, 2009, at 8:30 PM, Jeremy W. Sherman wrote: > > getxattr(2) will directly access the current on-disk attribute value. Why >> not just use it as Alastair suggested? >> > > Can you point to any official documentation for the Finder comment xattr > name? The storage for it has changed before, so looking in the xattrs > appears to be an implementation detail. > > -- > adam > > > >> On Tue, Apr 21, 2009 at 8:16 PM, Chris Idou <idou...@yahoo.com> wrote: >> >> >>> >>> I don't really want to be sending apple events to the finder since this >>> is >>> a background app, and it could be calling it fairly frequently, and I >>> believe this can impact the user's foreground use of Finder. >>> >>> Does anybody know what the issue is? Mostly the synchronization between >>> Finder Comments and spotlight seems instantaneous, but then on this >>> occasion >>> they seemed to refuse to sync. >>> >>> >>> >>> >>> ________________________________ >>> >>> >>> On Apr 21, 2009, at 8:04 AM, Chris Idou wrote: >>> >>> I've got a program which uses MDItemCopyAttribute to get the >>>> >>> kMDItemFinderComment, and I was playing around testing it, by changing >>> >>>> the value in the Finder and seeing if the value changed in my program, >>>> >>> and they ended up out of synch. It ends up that mdls returns a different >>> value than xattr -l, >>> >>>> and MDItemCopyAttribute doesn't return the up to date value. Now that >>>> its >>>> >>> out of synch, updating the value in Finder doesn't get it back in synch. >>> >>>> >>>> Is this expected behavior? Should I be using something other than >>>> >>> MDItemCopyAttribute to get the most up to date value? >>> >>> You should be sending an Apple event to the Finder: >>> >>> <http://www.cocoabuilder.com/archive/message/cocoa/2009/3/23/232927> >>> >>> --Michael >>> >>> >>> Enjoy a better web experience. Upgrade to the new Internet Explorer 8 >>> optimised for Yahoo!7. Get it now. >>> _______________________________________________ >>> >>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >>> >>> 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/jeremyw.sherman%40gmail.com >>> >>> This email sent to jeremyw.sher...@gmail.com >>> >>> _______________________________________________ >> >> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >> >> 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/amaxwell%40mac.com >> >> This email sent to amaxw...@mac.com >> > > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
