On 15 Apr 2009, at 19:44, Volker in Lists wrote:
You may want to download an example from Apple ;-) :
http://developer.apple.com/samplecode/DictionaryController/index.html
Thanks for this link. It did help me a lot.
One problem though:
If I bind the content of my dictionary controller to
I have My Array Controller which displays it's items
(NSDictionaries) in an NSTableView.
So far so good.
But now I want to have another NSTableView which has two columns Key
and Value and which shows all Key-Value-pairs of My Array
Controller.selection (or My Array
controller. Both are available automagically. I connected
the visibility of columns of a table view that way. My NSDictionary
held key/value pairs created from the column name and the hidden state
(bool). I have just yesterday thrown out the code, but it should be
coded/connected easily in 5
Hello Mr. Thomases:
First of all, thank you. For you, better than any of the others
provided me what I was looking for; the theory behind the system. That
was what I was looking for. This meal you served is a hearty one, and I
will not likely be able to consume it all in one sitting, but I
Others have addressed your concern about automated generation of
accessors to relieve the programmer of that drudgery. I'd like to
address something else...
On Jun 2, 2008, at 4:30 PM, john darnell wrote:
To refresh everyone's memory, key-value coding is the convention
that says
for
A good concrete example is the 'frame' property of CALayer. It is
calculated from other known values, and is not an ivar.
G.
On 4 Jun 2008, at 11:05 am, Ken Thomases wrote:
The important thing to think about is properties and what they
are. Properties are _not_ the ivars.
Hello everyone:
This is a discussion on theory and not a request for any practical help.
Please also be advised I am not trying to bash Cocoa or Objective-C; I
am simply curious why the designers of same built the language the way
they did. Understanding theory can sometimes geometrically
On Mon, Jun 2, 2008 at 10:30 PM, john darnell
[EMAIL PROTECTED] wrote:
I just read Hillegass' chapter that introduces Key-Value coding.
My question is, if this is such a necessary thing, why didn't the
designers simply design the compiler to auto-generate setter and getter
functions as per
On 2 Jun 2008, at 22:30, john darnell wrote:
Hello everyone:
This is a discussion on theory and not a request for any practical
help.
Please also be advised I am not trying to bash Cocoa or Objective-C; I
am simply curious why the designers of same built the language the way
they did.
On Jun 2, 2008, at 5:30 PM, john darnell wrote:
This is a discussion on theory and not a request for any practical
help.
Please also be advised I am not trying to bash Cocoa or Objective-C; I
am simply curious why the designers of same built the language the way
they did. Understanding
On Tue, Jun 3, 2008 at 5:41 AM, Hamish Allan [EMAIL PROTECTED] wrote:
On Mon, Jun 2, 2008 at 10:30 PM, john darnell
[EMAIL PROTECTED] wrote:
I just read Hillegass' chapter that introduces Key-Value coding.
My question is, if this is such a necessary thing, why didn't the
designers simply
11 matches
Mail list logo
