In my app running under 10.4.11 (and compiled against the 10.4 sdk), I am
finding that
outlineView:setObjectValue:forTableColumn:byItem:
messages are being sent in response to *single* clicks in outline view cells
in some cases. It appears this is true whenever the cell has non-empty
text. Noteably it happens in spite of the fact that
outlineView:shouldEditTableColumn:item:
returns false for these cells. My understanding from the doc is that the
setObjectValue method is called to handle the results of editing, and I
haven't seen mention of any other circumstance under which it is called.
So this is unexpected ... but also potentially useful to me, since
intercepting the setObjectValue message provides a way to detect single
clicks in an outline view under 10.4. It appears from the doc that the
methods related to mouse tracking in outline view cells require 10.5, and
10.4 is currently a requirement for this app. For example:
outlineView:shouldTrackCell:forTableColumn:item:
is listed as requiring 10.5 and I can't see another *supported* way of
intercepting a click in a cell, although double-clicks can be detected by
requests to edit a cell. At least that is what I've been able to figure out
so far, but my cocoa experience is limited.
I'd appreciate any comments on the issue of detecting clicks in outline view
cells as well as the possible reason for the unexpected setObjectValue
messages.
Thanks in advance.
-Kurt Bigler
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
