Not a problem, per se, I am just more comfortable with table views that
proactively read your model for their contents. Seems like with
NSMatrix I will have to store my own model to define what is displayed,
and then call methods on the matrix to basically duplicate my model in
its own internal model. Just seems inefficient.
I haven't really played with it yet, so I'm not sure exactly how much
merit my dual-model concerns deserves; it's just that I had expected it
to work like table views. They same to fulfill basically the same type
of need, just with a different method of layout.
Mike
On Dec 14, 2004, at 10:52 AM, John Stiles wrote:
It's not like you *have* to use NSMatrix :) There are other options.
What problem are you experiencing?
On Dec 14, 2004, at 10:50 AM, Mike R. Manzano wrote:
How positively depressing.
On Dec 14, 2004, at 10:45 AM, Fritz Anderson wrote:
On 14 Dec 2004, at 2:25 AM, Mike R. Manzano wrote:
Does NSMatrix have a datasource like NSTableViews? I can't figure
out how to supply it with data other than setting cells
individually.
You have fully grasped NSMatrix. It is a view that displays NSCells
in a grid, and provides some selection logic among them. There is no
datasource. There is only Cell.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
