Den 22:58 1. mars 2012 skrev Quincey Morris
følgende:
> You can *try* dealloc voodoo, but I think it's crucial to look at the
> observerInfo in the debugger. And, the number of remaining observers may be
> more informative than what they are.
Hi
Sorry it took a little while to get back to you.
On Mar 1, 2012, at 13:23 , Per Bull Holmen wrote:
> OK. I haven't thought of KVO-compliance at the level
> because no values can change at this level. Only the controller's
> parameterInfo property can change, by replacing it. That's what I
> meant by calling the parameterInfo object immutable. N
Den 21:42 1. mars 2012 skrev Quincey Morris
følgende:
> No, it's nothing to do with the mutability of the parameterInfo object.
>
> The problem is likely caused by lack of KVO compliance of your key path
> either at the or the level, or both. I think
> the console message suggests a place to se
On Mar 1, 2012, at 11:26 , Per Bull Holmen wrote:
> parameterInfo..
>
> "parameterInfo" is a literal key name, maps to a
> parameter in a plug-in, and must be resolved at run-time.
> is one of several attribute names, such as "minValue",
> "maxValue" etc. There is a value object that represent
On Mar 1, 2012, at 12:26 PM, Per Bull Holmen wrote:
> In my current project I have a controller object, that the view can
> bind to, with the following key path:
>
> parameterInfo..
>
> "parameterInfo" is a literal key name, maps to a
> parameter in a plug-in, and must be resolved at run-time.
Hi
In my current project I have a controller object, that the view can
bind to, with the following key path:
parameterInfo..
"parameterInfo" is a literal key name, maps to a
parameter in a plug-in, and must be resolved at run-time.
is one of several attribute names, such as "minValue",
"maxVal
