ome reason for it.
http://stackoverflow.com/questions/1028700/core-data-strange-bindings-error-on-re-opening-a-document-help
- Original Message
From: Kyle Sluder
To: Chris Idou
Cc: Jerry Krinock ; cocoa-dev@lists.apple.com
Sent: Wed, 7 April, 2010 11:21:28 AM
Subject: Re: Tricky bind
On Tue, Apr 6, 2010 at 5:28 PM, Chris Idou wrote:
> I don't know, it seems to me like having everything always in synch is nicer.
> The user can see immediately how changing one field is affecting the other.
> And it used to work.
That will wreak havoc with Undo. Continuously updating values is
ed, 7 April, 2010 10:24:18 AM
Subject: Re: Tricky binding and continuous update problem
On 2010 Apr 06, at 16:36, Chris Idou wrote:
> If I turn off Continuously Update Value, it works sensibly,
Turn it off. Look at any of Apple's Sample Code. Also, Cocoa Design Rule #1:
If something
On 2010 Apr 06, at 16:36, Chris Idou wrote:
> If I turn off Continuously Update Value, it works sensibly,
Turn it off. Look at any of Apple's Sample Code. Also, Cocoa Design Rule #1:
If something is off/on by default, don't change it unless you're knowingly
doing something weird.
> albeit
I've got a problem that I had working, but my app suddenly seems broken, and
I'm not sure if I did something or what. All I know is old versions of my app
work, but now my code base doesn't.
I've got a UI with a NSTableView at the top, and some individual fields at the
bottom. Typical UI wher
