FROM : Jens Alfke
DATE : Sun Jun 22 18:26:08 2008
On 22 Jun '08, at 8:41 AM, William Squires wrote:
> If I hover the mouse over the content region of the NSTableVIew, a
> spurious tableView:objectValueForColumn:row shows up in the console
> log (note that I'm not clicking on anything, just hovering the mouse
> over the NSTableView)
I'd guess this is due to the Leopard feature that shows the entire
cell contents in a tooltip-like floating view after you've hovered
over the cell for a second. It has to get the cell contents and then
measure the pixel width to see if it fits in the cell, before deciding
to show the expansion view.
(Remember, the table never remembers the contents of any table cells!
Any time it has to get the value in a cell, it asks your data source
for it. That's what makes NSTableView scalable to millions of rows.
Don't worry about it; it's a feature.)
—Jens
DATE : Sun Jun 22 18:26:08 2008
On 22 Jun '08, at 8:41 AM, William Squires wrote:
> If I hover the mouse over the content region of the NSTableVIew, a
> spurious tableView:objectValueForColumn:row shows up in the console
> log (note that I'm not clicking on anything, just hovering the mouse
> over the NSTableView)
I'd guess this is due to the Leopard feature that shows the entire
cell contents in a tooltip-like floating view after you've hovered
over the cell for a second. It has to get the cell contents and then
measure the pixel width to see if it fits in the cell, before deciding
to show the expansion view.
(Remember, the table never remembers the contents of any table cells!
Any time it has to get the value in a cell, it asks your data source
for it. That's what makes NSTableView scalable to millions of rows.
Don't worry about it; it's a feature.)
—Jens
| Related mails | Author | Date |
|---|---|---|
| William Squires | Jun 22, 17:41 | |
| Daniel Richman | Jun 22, 17:43 | |
| William Squires | Jun 22, 17:43 | |
| Jens Alfke | Jun 22, 18:26 | |
| Michael Ash | Jun 23, 02:32 |






Cocoa mail archive

