On 14 Dec 2012, at 11:13, Mike Abdullah wrote:
> I'd strongly advise the OP it's better for them to create a custom class for
> their model objects, rather than go down this route of globally modifying
> NSMutableDictionary's API.
In general I would strongly advise this too, which effectively
I'd strongly advise the OP it's better for them to create a custom class for
their model objects, rather than go down this route of globally modifying
NSMutableDictionary's API.
On 13 Dec 2012, at 22:18, jonat...@mugginsoft.com wrote:
> On 13 Dec 2012, at 11:54, jonat...@mugginsoft.com wrote:
>
On 13 Dec 2012, at 11:54, jonat...@mugginsoft.com wrote:
> I bind an NSArray of NSMutableDictionary instances to an NSTableView and
> enable NSTableColumn editing..
>
> How can I best implement KVO based validation when editing the view?
>
> Subclassing NSArray controller is a no go as validate
I bind an NSArray of NSMutableDictionary instances to an NSTableView and enable
NSTableColumn editing..
How can I best implement KVO based validation when editing the view?
Subclassing NSArray controller is a no go as validateValue:forKeyPath:error is
never called.
Subclassing the NSMutableDict
