NSTableView thoughts (or afterthoughts)
NSTableView thoughts (or afterthoughts)
- Subject: NSTableView thoughts (or afterthoughts)
- From: Stephane <email@hidden>
- Date: Wed, 8 Nov 2006 17:25:45 +0100
o In NSTableView.h, why are not all the parameters of NSTableView *
type not using the same name? We have tv, tableview, aTableview?
Enhancement request filed in Radar.
o Why is editColumn:row:withEvent:select editing the wrong row when
it's invoked from the contextual menu of the tableview?
1. Select row with mouse
2. Control + Click
3. Select a command that:
i. add a row to the data source's data
ii. reload the data
iii. select the last row of the table view
iv. edit the last row of the table view
Result:
previously selected row (with the mouse) is edited.
I can delay the edition but it seems really strange (the index is OK
since the last line is correctly selected).
o Is there any sense in the different "Resizing Mode"? Uniform,
Sequential, Reverse Sequential are just producing very unpredictable
result when the current width for columns is to be decreased.
o Why is a vertical scroller displayed when a column is hidden and
there's plently of space between the last row and the bottom of the
tableview?
o Not directly related to NSTableView, but isn't there something
easier than:
[myMutableArray insertObjects:myArray atIndexes:[NSIndexSet
indexSetWithIndexesInRange:NSMakeRange(myLocationInMyMutableArray,
[myArray count])]];
to insert an array of objects?
[myMutableArray insertObjects:myArray atIndex:
myLocationInMyMutableArray] anyone?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden