Key-Value coding is greatly emphasized in Cocoa...well, it is now! ( Ch 7 Hillegas and Apple documentation).
But, reading all this, ( Bindings use KVC, make sure your code complies with KVC coding , you can use a string to access the properties of another object, etc etc), I still do not have a feel for what it is **about** KVC that makes it so powerful.
Can anyone take a crack at distilling the essence of KVC.
So, for example, what **can** one do because of KVC that would be really difficult to do without it.
Or..What is it about code that **does** conform to KVC that makes it so much better than code which does not?
Perhaps I am missing something, and that's why I would love to hear from those for whom KVC is so important.
Thanks as always.
But, reading all this, ( Bindings use KVC, make sure your code complies with KVC coding , you can use a string to access the properties of another object, etc etc), I still do not have a feel for what it is **about** KVC that makes it so powerful.
Can anyone take a crack at distilling the essence of KVC.
So, for example, what **can** one do because of KVC that would be really difficult to do without it.
Or..What is it about code that **does** conform to KVC that makes it so much better than code which does not?
Perhaps I am missing something, and that's why I would love to hear from those for whom KVC is so important.
Thanks as always.