Problem somewhat solved. Landed up subclassing nstableview and
overriding mouseDown:
Works well (at least on my machine).
On Feb 2, 2010, at 9:08 AM, Corbin Dunn wrote:
Table b should be set to setAllowsMultipleSelection:NO. However,
despite that, you can programmatically change the selectio
Thanks Corbin,
So this is the rub: If I just set allowsMultipleSelection: NO in
interface builder and don't set allowsMultipleSelection:YES
[programmatically right before doing the setSelected... (though I have
to support 10.2-?? so I am still using setSelectedRow...)] I get the
followin
Matthew -- I believe there was a problem with < 10.5 asserting; that has been
fixed, but you have to link on 10.5+ to get the "fixed" behavior (for
compatibility reasons). I suggest requiring your uses to upgrade :)
However, you should be able to do -setAllowsMultipleSelection:YES, select the
r
Table b should be set to setAllowsMultipleSelection:NO. However, despite that,
you can programmatically change the selection yourself with
-setSelectedRowIndexes:byExtendingSelection: when the selection in Table A
changes.
--corbin
> I have 2 tables that basically have a many to many relations
On Feb 2, 2010, at 8:32 AM, Matthew Weinstein wrote:
> Still trying to find a way to turn off setAllowsMultipleSelection just as the
> table becomes the responder. Is there some way of anticipating this, a
> "willbecomefirstresponder" kind of a notification?
What are you really trying to do? O
Still trying to find a way to turn off setAllowsMultipleSelection just
as the table becomes the responder. Is there some way of anticipating
this, a "willbecomefirstresponder" kind of a notification?
Thanks in advance, Matthew Weinstein
___
Cocoa-d
