So, there is no way to know that the method is correctly implemented
for a given cell subclass just by it checking if it is present
(since it is always present). Because of that, we have to check for
the app to be linked against Leopard.
OK, I see, that makes sense.
Mani, in regard to your original problem -- how did you limit an
editing session on Tiger?
If I remember correct, I overwrote the trackMouse:... routine of the
cell. If the user clicks on the special area of my NSTextFieldCell
subclass, I am doing something else. But the single click editing
seems to happen at another level (most probably in the NSTableView
mouseDown code, I think).
But I was able to solve my problem. I found a way to disable the
single click editing on Leopard, so the app behaves exactly like on
Tiger. (I did not find a solution to get the desired behaviour plus
single click editing on Leopard. But that's not so critical in my case
and I spent no more time into that.)
Side note: there is a way to disable the single-click editing behavior
There is: I just always return NO in the tableview delegate method
tableView:shouldEditTableColumn:row:.
I still can start an editing session programmatically
(editColumn:...), if I want to. In my case editing is only available
through a contextual menu. Double clicking is overwritten with another
action that makes more sense in my app (but I think it must be
possible to start an editing session here if I would have wanted that,
too).
Regards,
Mani
--
http://www.mani.de
iVolume - Loudness adjustment for iTunes.
LittleSecrets - The encrypted notepad.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
