Re: two tables, one button
Re: two tables, one button
- Subject: Re: two tables, one button
- From: Chris Silverberg <email@hidden>
- Date: Wed, 11 Jun 2003 11:09:33 -0700
- Organization: Silverberg.Net
on 6/11/03 10:30 AM, Brent Gulanowski at email@hidden wrote:
>
I am concerned that you are using an implementation concept
>
(responders) when discussion user interface behaviour. What is the
>
user's impression? What distinguishes the possible selected items in
>
the table views?
The use of the 'responders' terminology was just for the benefit of the
list. In user terminology, the button needs to follow two tables and it
needs to track which table has *user focus*.
I'm not sure quite how to answer your question. Look at iTunes for
example... depending on your view you may see up to four tables...
playlists, artists, albums, songs. Each table may have a selection, but
only one table has user focus. (You can see the one that has user focus by
the one that has the line highlighted in blue rather than gray).
In iTunes, the File menu has a menu item for 'Get Info' that that will be
enabled/disabled according to which list has user focus. Now imagine if
iTunes had a 'Get Info' button. That is what I'm trying to accomplish.
>
Every time you select an item in a table, it will send an action
>
message to its target.
Ah, okay... this helps. I'm not in the habit of thinking of NSTableView as
a control so I hadn't considered having the table target my window
controller. This is better than NSTableViewSelectionDidChangeNotification
because the target gets invoked even if you are clicking on an already
selected item.
One problem for the future... I suspect this is going to break if I want to
allow tabbing between tables. Will the target be invoked if the table
gains/loses focus...? I suspect it wont.
Since NSTableView doesn't seem to respond to tab for nextKeyView I'm
probably not going to implement this now. But I may come back to it in the
future.
>
How does the user select a table without selecting an item in the
>
table?
If you have a table that already has a selected item but is not the focused
table, the user can click on that item to make the table have focus.
However, the selection did not change so no notification was sent. However,
as you pointed out... the target *is* invoked because the user is clicking
on an item so I can use that instead.
thanks much,
-Chris
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.