Hate to reply to my own question, but I've actually found something
else--
In my tableview's subclass' inLiveResize: method, if i return NO,
essentially tricking the tableview into thinking it's always
"finished" dragging, and therefore it actually updates the
tableview's content live, with the resize. Granted, I realize this
isn't necessarily a good thing (read: I can forsee quite a few
problems by never having it return "yeah, im in a live resize now."
However, even with this as you may guess, it doesn't move the table
column headers with it.
Thoughts?
On Nov 9, 2006, at 9:47 AM, Brian Amerige wrote:
Hi all,
I know I've asked this question before, but I've actually learned
a little bit more about what's going on behind a live Resize in an
NSTableView. Given that, I've also noticed one additional thing.
My tableview actually performs exactly what it's supposed to, but
only without data. It'll resize all columns uniformly, perfectly.
The problem is, as soon as data is added to the tableView (not a
lot of data either, I've tested with everything from one to one
hundred rows), the behavior of the live resize is significantly
different. While it appears to call sizeToFit: just the same as
without data, it doesnt' seem to have any affect. It waits until
I've finished resizing to send the sizeToFit: call, where it actually
I've tried over-riding inLiveResize: to tell it to call sizeToFit:
every no matter what (right before I return [super inLiveResize]),
but the resize artifacts still seem evident.
I know others have been asked this, and I definitely know it's
possible, but again, there doesn't seem to be a succinct answer. Is
it a bug in NSTableView we've got to fix via our subclasses?
Open to any comments,
Brian.
_______________________________________________
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
