Erik Buck wrote:
Enabling empty selection in IB should do the trick. You can also control selection programmatically with the delegate. http://developer.apple.com/library/mac/#documentation/Cocoa/Reference/NSTableViewDelegate_Protocol/Reference/Reference.html
That looked promising, but tableView:shouldSelectRow: does not get called when the window appears after being created or hidden. Nor does it get called if I click the selected row. It does get called if I click in an empty row and then back in a row with data.
Out of curiosity: Why not allow selection? Users might want to copy and paste information about documents. Selection doesn't have to mean editable._______________________________________________
Interesting thought - I guess there might actually be some use to allowing selection and copy. I am experimenting with replacing a Carbon window with a Cocoa one in an otherwise Carbon application, so I'm trying to limit the amount of impact on the rest of my code. Enabling copy would mean more changes than I'm interested in at this point, but I'll put that on my list for further examination.
John -- John Brownie, john_brow...@sil.org or j.brow...@sil.org.pg Summer Institute of Linguistics | Mussau-Emira language, Mussau Is. Ukarumpa, Eastern Highlands Province | New Ireland Province Papua New Guinea | Papua New Guinea _______________________________________________ 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 arch...@mail-archive.com
