> On Aug 4, 2016, at 11:34 PM, livinginlosange...@mac.com wrote:
>
> I have 8 NSComboBoxes in my application organzied into 4 pairs, each pair
> sharing an NSComboBox delegate. I have had some users periodically say that
> the combo-boxes get confused. ComboBox A will wrongly display ComboBox B
I am considering moving an app to Core Data. Currently it manages an array
of InterestingObjects. I use NSArrayControllers and TableViews. Everything
works.
I have two cases:
1. I have one array of all InterestingObjects and I set different predicates
on the array controller to show only those ma
I have an app running only on iPad right now that uses CoreData. From time
to time, I receive updated data from the server which forces me to clean up
my local database.
I would like to be able to delete small chunks of data in the background
but I don't find any appropriate key for UIBackgroundMo
On Aug 5, 2016, at 07:03 , Keary Suska wrote:
>
> One would think that it either has to do with the assignment of the delegate
> or the assignment of the outlets/properties of the delegate, or both.
I would add one other thing to this “smells like” list: duplicate controls. If
you somehow ende
On Aug 5, 2016, at 07:46 , Trygve Inda wrote:
>
> Somehow this seems easier to do without Core Data.
If you’ll accept my opinion as commentary and not anything more dire, I’d say
that your proposed course of action is based on several clearly undesirable
options:
1. For 5,000 records, I don’t
Little different perspective, Core Data tends to work drop dead easy for
simple stuff. Small data set with simple functionality should work straight
out of the box easy.
And there is nothing wrong with creating a manual array of managed objects
from a Core Data result set.
I personally wouldn't s
> On 6 Aug 2016, at 12:46 AM, Trygve Inda wrote:
>
> I am considering moving an app[…]
> Everything
> works.
So my question is: what is your motivation?
Is it underperforming?
Is it just idle curiosity, restlessness, too much time on your hands, or some
other state of mind? While I have s
> Little different perspective, Core Data tends to work drop dead easy for
> simple stuff. Small data set with simple functionality should work straight
> out of the box easy.
>
> And there is nothing wrong with creating a manual array of managed objects
> from a Core Data result set.
Currently I
