Ok, that sounds like a good place to start. Thanks very much for the
insight. I would very much appreciate a look at your code as I'm
very new to Cocoa programming (have only had a Power Mac since last
October). Cocoa reminds me very much of the Qt toolkit from
Trolltech but there are substantial differences, such as this matter
of how the Table View works.
Thanks
-Greg
On Jun 1, 2005, at 12:12 AM, Lee Morgan wrote:
I recommend using two nstextfieldcells within your cell subclass.
Using views within cells can be... well painful, due to the way
cells draw themselves - plus using a view (or two) within a cell
has extra memory and cpu costs that you simple don't need to deal
with since you simply want two vertical text field cells.
To get the thin black line you'll simply use quartz to draw the line.
- lee
P.S. I'm finishing up my LMStatusCell sublcass (which displays a
nsprogressindicator or a image) - I can give you the source to it
in a few days if you like - it might save you some time trying to
learn how to subclass nscell (and nscontrol).
Only problem is, I can't find a way to expose extra bindings for my
cell in Interface Builder.
On May 31, 2005, at 8:24 PM, Gregory Olds wrote:
Ok, that makes sense but I'm not sure how to properly subclass
NSCell. What I want to do is put 2 text fields in a sell (one on
top of the other) separated by a thin black line. So do I make a
custom view that looks like what I want and then have the custom
cell draw this custom view inside itself? This would seem to lose
the lightweight advantage of the NSCell.
_______________________________________________
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
