> 3. Row selection > In this pattern, the user selects a row (or multiple rows) and then > presses a button found on a toolbar above the list. Buttons should > enable and disable based on the selection. Benefits: removes screen > clutter, allows for actions on multiple items. Drawbacks: two-click > interaction, actions and items are not directly connected.
Jack, you mention "buttons should enable and disable based on the selection". Have you had success with this in the past? I am worried about randomly disabling buttons -- what if the user doesn't understand why it's happening? (In my situation, I'd be disabling certain items when the user selects multiples -- because some actions can't be done to more than one item at a time.) I just imagine this would be confusing to users and I can't find any decent examples. I'm wondering if someone has come up with some elegant feedback mechanism -- like a button greys out and next to it is something saying "some actions can only be performed on one item at a time" -- but ugh, this seems so ugly! Meredith - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Meredith Noble Information Architect, Usability Matters Inc. 416.598.7770 x6 [EMAIL PROTECTED] http://www.usabilitymatters.com - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
