Re: tables cells and views
Re: tables cells and views
- Subject: Re: tables cells and views
- From: Andy Lee <email@hidden>
- Date: Sun, 28 Apr 2002 14:25:03 -0400
At 8:02 PM +0200 4/28/02, Ondra Cada wrote:
On Sunday, April 28, 2002, at 07:50 , Andy Lee wrote:
One difference from what you describe is that OmniWeb does not put
a Cancel button in each cell. It puts a single button for that
purpose at the top of the window. Likewise, Internet Explorer
provides a contextual menu rather than a Cancel button for each
item being downloaded. I'm not saying these are better UI
designs...
I am, actually. Subjective preferences aside, per-line buttons would
prevent you from stopping more tasks at once,
No, you'd just have to click once in each cell that you want to stop.
This puts a slight delay between the stoppings, but surely that
doesn't matter -- they aren't going to be perfectly simultaneous
anyway. If you have two non-contiguous cells that you want to
cancel, per-line buttons actually require fewer clicks than the
single-button-at-the-top (2 vs. 3). On the other hand, if you have 5
contiguous cells, the button-at-the-top is quicker: you can drag to
select all five and then click once.
I didn't mean to favor one approach or the other. Mass cancellations
(at least in Web browsers) are rare, so either approach is probably
fine as long as it's clear how it works and it suits the likely usage
patterns in the app in question. For example, if you have operations
other than Cancel that the user might want to apply to multiple
cells, then the apply-operation-to-selection approach probably makes
more sense than putting five buttons in each cell.
whilst a combination of them *and* a "stop selection" one would be
confusing indeed.
I agree that would be bad. I would use one xor the other.
--Andy
_______________________________________________
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.