I think you need to apply to Apple and get a provisioning profile, even if the
app isn't sandboxed:
https://developer.apple.com/forums/thread/653890
--Michael
> On Mar 14, 2021, at 5:43 AM, Allan Odgaard via Cocoa-dev
> wrote:
>
> I’ve tried something like the code below to save a file not o
I found that this problem occurs if the non-TextEdit editor uses safe saving
(FSPathReplaceObject or -[NSFileManager replaceItemAtURL:...]), whereas
TextEdit doesn't complain if the app just writes directly to the file. Filed as
rdar://9978155.
--Michael
On Sep 19, 2011, at 2:26 PM, Boyd Coll
On Aug 1, 2010, at 2:26 PM, Michael Thon wrote:
> I decided to spend more time on Search Kit first, to see if I can get it to
> do what I want. As far as I know it is the basis of Spotlight, so I didn't
> think I would have problem indexing large numbers of files.
You'd think so, but I, too,
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
On Mar 23, 2009, at 12:19 AM, Adam R. Maxwell wrote:
Using the MDItem C API had none of the AppleScript/Apple event
problems, and was a small fraction of the code.
On the other hand, MDItem will probably fail if the file is on a
volume for which Spotlight is disabled or its index isn't up-t
of your application) or it doesn't. If
it doesn't, you will need to use -finalize. It seems to me that this
is unrelated to how the lifetime for the CFTypeRef is managed.
As noted in my reply to Michael Tsai, I do not call
CFMakeCollectable. But I DO declare my CFTypeRef v
On Mar 16, 2009, at 2:08 PM, Bill Cheeseman wrote:
I am looking for a strategy to avoid implementing a -finalize method
in a garbage-collected Objective-C class that declares a CFTypeRef-
style Core Foundation instance variable. I believe this is a fairly
common problem, because any Cocoa wr
n where it would be preferable
to NSConditionLock. Apple confirmed the bug and said that they will
document NSCondition as requiring 10.5.
--
Michael Tsai <http://c-command.com>
___
Cocoa-dev mailing list (Cocoa-dev@l
