FROM : Corbin Dunn
DATE : Wed Jul 26 00:41:30 2006
On Jul 25, 2006, at 12:35 PM, Mike Abdullah wrote:
> The biggest problem I've found is how NSCell works. The table view
> only uses one NSCell to do its drawing. Rather than having a cell
> for each row of the table, it has a single cell that is copied and
> released as appropriate.
>
This is actually a feature! It makes tables have good performance.
> Obviously, what you want to do instead is have an instance of your
> cell for each row of the table. If you're using 10.4 only, a good
> workaround may be to use the cellForRow: method.
>
You mean, dataCellForRow:, and it is a method on NSTableColumn that
you must subclass and override to return a custom cell.
-corbin
(PS: WWDC plus: i'll be covering this and more in the "Beyond Buttons
and Sliders" talk at WWDC)
DATE : Wed Jul 26 00:41:30 2006
On Jul 25, 2006, at 12:35 PM, Mike Abdullah wrote:
> The biggest problem I've found is how NSCell works. The table view
> only uses one NSCell to do its drawing. Rather than having a cell
> for each row of the table, it has a single cell that is copied and
> released as appropriate.
>
This is actually a feature! It makes tables have good performance.
> Obviously, what you want to do instead is have an instance of your
> cell for each row of the table. If you're using 10.4 only, a good
> workaround may be to use the cellForRow: method.
>
You mean, dataCellForRow:, and it is a method on NSTableColumn that
you must subclass and override to return a custom cell.
-corbin
(PS: WWDC plus: i'll be covering this and more in the "Beyond Buttons
and Sliders" talk at WWDC)
| Related mails | Author | Date |
|---|---|---|
| Thom McGrath | Jul 24, 21:57 | |
| I. Savant | Jul 24, 22:01 | |
| Shawn Erickson | Jul 24, 22:03 | |
| Mike Abdullah | Jul 25, 21:35 | |
| Corbin Dunn | Jul 26, 00:41 | |
| Mike Abdullah | Jul 26, 01:24 | |
| Chris Suter | Jul 26, 02:31 | |
| Corbin Dunn | Jul 26, 05:19 |






Cocoa mail archive

