On Jun 21, 2013, at 14:10 , Rick Mann wrote:
>
> On Jun 21, 2013, at 14:03 , Kyle Sluder wrote:
>
>> On Fri, Jun 21, 2013, at 01:55 PM, Rick Mann wrote:
>>> But Core Data complains that activeChild is misconfigured because it
>>> doesn't have an inverse. But I have no need for an inverse, why
On Jun 21, 2013, at 14:03 , Kyle Sluder wrote:
> On Fri, Jun 21, 2013, at 01:55 PM, Rick Mann wrote:
>> But Core Data complains that activeChild is misconfigured because it
>> doesn't have an inverse. But I have no need for an inverse, why does Core
>> Data?
>
> Apple's explanation, straight fr
On Fri, Jun 21, 2013, at 01:55 PM, Rick Mann wrote:
> But Core Data complains that activeChild is misconfigured because it
> doesn't have an inverse. But I have no need for an inverse, why does Core
> Data?
Apple's explanation, straight from the docs:
http://developer.apple.com/library/mac/documen
I find myself frequently wanting to do something like this:
Parent
children to-many to Child
activeChild to-one to Child
Child
parent to-one to Parent
But Core Data complains that activeChild is misconfigured because it doesn't
have an inverse. But I have no need for an inverse
I'm getting a lot of strange log entries from a program that uses AVFoundation.
Vide
/SourceCache/AppleGVA/AppleGVA-5.0.6/Sources/Slices/Driver/AVD_loader.cpp:
failed to get a service for display 3
AVF encoder info: AVF_SetParam kAVF_Encoder1_ProfileLevelUpdateParam, reset
profile_level from 1
On Jun 21, 2013, at 03:40 , Markus Spoettl wrote:
> can it be that a wrapper which I hold on to from the time I first created it
> switches it's backing from in-memory to memory mapped disk once it has been
> saved?
There are actually three possible states for a regular file wrapper:
1. 'regu
On 6/21/13 8:19 AM, Quincey Morris wrote:
What is interesting too is that my application was able to create the whole
wrapper structure when it first created the package. It would have required
the same amount of memory to hold the wrappers in memory before they get
written to the disk by UIDocum
On 20 Jun 2013, at 23:50, Quincey Morris
wrote:
> On Jun 20, 2013, at 15:12 , Mike Abdullah wrote:
>
>> There should be no need to do this. If you need a location on disk for the
>> document, just trigger an autosave so that the system effectively creates a
>> temp location for you to use (
