Re: Checkbox Mayhem

2016-12-18 Thread Quincey Morris
On Dec 18, 2016, at 12:17 , Frank D. Engel, Jr. wrote: > > I had been using @dynamic for object types and @synthesize for basic types > (such as BOOL and int). It seems I will need to create the accessors then > for the basic types as I just tried and @dynamic does not work for those. You hav

Re: Checkbox Mayhem

2016-12-18 Thread Frank D. Engel, Jr.
I see... I had been using @dynamic for object types and @synthesize for basic types (such as BOOL and int). It seems I will need to create the accessors then for the basic types as I just tried and @dynamic does not work for those. Thank you! On 12/18/2016 10:15, Keary Suska wrote: On D

Re: Checkbox Mayhem

2016-12-18 Thread Keary Suska
> On Dec 18, 2016, at 5:50 AM, Frank D. Engel, Jr. wrote: > > My guess is that for some reason the @synthesize methods are not calling > "willChangeValueForKey" and the like - why would that be the case? I have > worked on one or two other Core Data projects and I don't remember having to >

Re: Checkbox Mayhem

2016-12-18 Thread Frank D. Engel, Jr.
Ok, I think I'm getting closer to understanding this: When I add new rows to the table, I can update the checkboxes before exiting the application, and the values stick (though the enabled state of "a" does not change when I toggle "b"). When I re-open the application after that, the enabled

Checkbox Mayhem

2016-12-18 Thread Frank D. Engel, Jr.
Hoping this is something simple that is simply escaping me at the moment... I a view-based table with two columns containing checkboxes. The table has its content property bound to an array controller's arrangedObjects, with that array controller being tied to entities in Core Data. The che