Where can I find Debug & Profile Libraries for 10.6 ?

Hi lists, I'm cross posting because this was already discussed in both lists, sorry for that. I'm looking the the Debug & Profile libraries that have been discussed here http://lists.apple.com/archives/cocoa-dev/2008/Mar/msg01098.html and http://developer.apple.com/mac/library/technotes/tn2

Re: CoreData database sharing and migration

Hi Ben, Can you be kind enough to explain how Apple frameworks do that ? (multiple processes, single machine, one SQLite database) I'm thinking of CalendarStore, AddressBook framework. Can you describe what is the general idea behind those Apple frameworks? Aurélien, Objective Decision Team

[Core Data] mergeChangesFromContextDidSaveNotification: and thread safety

Hi ! I'm having strange crashes in my threaded core data application. Happy WWDC is in few days! Core Data multithreading basic rule is to avoid passing managed objects across threads, and pass objectIDs instead. To "synchronize" 2 mocs from 2 different threads (sharing the same psc), I

Re: [Core Data] mergeChangesFromContextDidSaveNotification: and thread safety

Thanks for the explanation, I like when you have to bend the rules ;) Aurélien, Objective Decision Team On 29 mai 09, at 23:25, Ben Trumbull wrote: On May 29, 2009, at 2:49 AM, Aurélien Hugelé wrote: Core Data multithreading basic rule is to avoid passing managed objects across

Re: Long term performance of NSConnection

Are you sure you are not instantiating/creating/opening a connection each time? are you really reusing the same connection? Aurélien, Objective Decision Team On 2 juil. 09, at 21:29, Kevin Brock wrote: We've got an application that uses some NSConnection objects to call between binaries

Core Data mergeChangesFromContextDidSaveNotification: does not *completely* update the context ?

Hi! I think mergeChangesFromContextDidSaveNotification: does not work as most people expect: I have a mainthread and a subthread. My subthread updates a managed object (change one of the property value) and save. In the mainthread, I use [mainThreadContext mergeChangesFromContextDidSaveNotifica

Re: Core Data mergeChangesFromContextDidSaveNotification: does not *completely* update the context ?

objects are definitely refreshed, so why does NSRefreshedObjects key is not in the didSaveNotification ? Aurélien, Objective Decision Team Le 20 déc. 2010 à 06:49, Aurélien Hugelé a écrit : > Hi! > > I think mergeChangesFromContextDidSaveNotification: does not work as most > people

Re: Core Data mergeChangesFromContextDidSaveNotification: does not *completely* update the context ?

:49 PM, Aurélien Hugelé wrote: > >> Hi! >> >> I think mergeChangesFromContextDidSaveNotification: does not work as most >> people expect: >> I have a mainthread and a subthread. My subthread updates a managed object >> (change one of the property

Re: NSBlockOperation with +[sendSynchronousRequest sendSynchronousRequest:...] or async?

Always use the async API. For networking, there are *tons* of reasons to avoid your own threading (ie, CPU -> battery consumption) when Apple does all that for your using their Async API (and only one global thread to manage the network) Look at the free WWDC videos from 2010, this is very well e

Re: DO problems

a solution? Thanks, Ben Einstein On Mar 25, 2008, at 9:12 AM, Aurélien Hugelé wrote: I encountered this very same problem with DO since Leopard. I noticed that a large part of the DO backend has been rewritten in Leopard. If you know how to fix/reproduce the problem, I'll be glad to know. I

Re: DO woes

See "DO problems" posted just few days ago. Aurélien, Objective Decision Team On 29 mai 08, at 00:39, Western Botanicals wrote: Cocoa Experts, Thank you for your time. I am having a problem with DOs. I am working on this time clock system to track the timecards of employees. The followi

Re: NSCalendarDate to be deprecated

I too find NSCalendarDate tremendously useful. The fact that it is used (not to say necessary) in Sync Services let me believe it won't be deprecated. I hope Apple won't ask 3rd party developer dto rewrite their code using Sync Services ... Aurélien, Objective Decision Team On 18 août

Re: DO problems

I encountered this very same problem with DO since Leopard. I noticed that a large part of the DO backend has been rewritten in Leopard. If you know how to fix/reproduce the problem, I'll be glad to know. I suggest trying your program on a Tiger/Tiger configuration.. I'm pretty sure it will

[Core Data] Difference between objectWithID: and a fetch "self IN %@", someObjectIDs ????

Hi list ! I have a subthread that sends to my main thread some objectIDs (of objects it inserted in the same store (same PSC)) I have 2 MOCs, one per thread, sharing the same PSC (following advices from the doc...) In the main thread, using objectWithID: repeatedly on each objectID sent b

Re: [Core Data] Difference between objectWithID: and a fetch "self IN %@", someObjectIDs ????

Hmmm, It seems I was using temporary objectIDs, not permanent ones... It was a nightmare with 10.4 because there was no way to get permanent objectIDs... now we can, and I've been overlooking that problem ;) Aurélien, Objective Decision Team On 20 mai 09, at 12:03, Aurélien H

Re: [Core Data] Difference between objectWithID: and a fetch "self IN %@", someObjectIDs ????

12:03, Aurélien Hugelé wrote: Hi list ! I have a subthread that sends to my main thread some objectIDs (of objects it inserted in the same store (same PSC)) I have 2 MOCs, one per thread, sharing the same PSC (following advices from the doc...) In the main thread, using objectWithID: repeatedly on

Re: [Core Data] Difference between objectWithID: and a fetch "self IN %@", someObjectIDs ????

That's very clear, thanks for the explanation! Aurélien, Objective Decision Team On 20 mai 09, at 21:15, Ben Trumbull wrote: In the main thread, using objectWithID: repeatedly on each objectID sent by the subthread returns the object that was inserted in the background thread. This is exac

[Core Data] Can we use setValue:forKey: in *willSave* method of NSManagedObject?

Hi list! In the documentation it is clearly stated that we should not trigger change notifications in the *didSave* method of NSmanagedObject. The willSave method is not very well described. In particular, can we use setValue:forKey: (or trigger change notifications) inside it? I usually d