The user has an NSTableView in which is presented a number of elements
( 1 per row, typically 20 - 200 rows ) out of which they need to
produce a number of sequenced sub groups.
The user presses the 'Start Sub Group' key ( i.e. clear the sequence
selection cache ) and then by picking a possible sequence ( one row/
element at a time ) they build a group.
As the group is selected, further info about that particular sub group
of elements is presented.
They can close/abort/store a given sub group at any time.
Peter
On 15 Oct 2009, at 00:12, Graham Cox wrote:
On 15/10/2009, at 10:01 AM, Peter Hudson wrote:
I have tackled this problem by using the NSTableView delegate
method tableViewSelectionDidChange:
In this method I query the table for selected rows and then compare
with the index set from the previous call to
tableViewSelectionDidChange: I simply store the incremental
changes in sequence.
Like Kyle I'm curious about the rationale for this. Since there's no
indication of how time played its part in coming up with the
selection, doesn't this lead to strange behaviour for the user? What
if I made a selection, got interrupted and only got back to work
several hours later? How would what happened next make sense given
that I'd almost certainly forgotten the selection sequence and had
no feedback to remind me? Or does the selection get reflected in a
second list that shows the sequence? That would make more sense but
a pure selection with a hidden time element seems like a problematic
UI to me.
--Graham
_______________________________________________
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
