Rex Kilian <[email protected]> wrote: > Even though you can drag the labels to the messages there are no drag > handles on the labels. I'm interested to hear discussion about > certain drag-able items having drag handles and others not. In the messages list all the pixels are "hot". i.e.: linked to the message displaying, and it happens at the mouse down event which is somehow unusual. All pixels but a few: the selection checkbox, the star. Hence the need for a specialized area to react only to the drag & drop action.
The lack of affordabilities in the labels is, IMO, a missing item. In fact, I was not aware of this feature. Not drawing a handle on the label might have been done on purpose, to avoid visual clutter. But the label should react and publish its capability at the mouse hover. Notice that you can also drag "Starred" or "Trash" to a message but nothing happens. This seems to me not fully baked yet. -- Juan Lanus On Fri, Jul 24, 2009 at 12:26, Rex Kilian <[email protected]> wrote: > Back to the interaction... > > You are also able to drag the label to the message when the message > is in the list or when you have the message open. I have actually > moved to using this interaction more as it allows me to "label" the > message without having the message get tagged and archived all in one > step. For those that don't know when a message is archived it is > removed from the main list of messages. Currently if you drag the > message to the label using the drag handles it will do both a > "label" and an "archive". I often want to label a message but > have it remain visible in the list, i.e tag it. > > Even though you can drag the labels to the messages there are no drag > handles on the labels. I'm interested to hear discussion about > certain drag-able items having drag handles and others not. And then, > if the labels had drag handles how should the interface communicate > that dragging labels will only perform a "label" steps, but > dragging a message with perform "label-AND-archive" steps? Or is > this a case where the context of what is being dragged will dictate > what steps are performed? (Personally I would disagree with the last > statement because I was surprised that it archived my message when I > drug it to a label, but maybe that's just me.) > > Perhaps the reason that drag handles are not on the labels is that > the design rationale is meant to direct users to drag messages and > not labels. Perhaps the design rationale is providing a 'hidden > alternative' so people like myself aren't locked out of an inverse > interaction, inverse meaning drag 'label to message' instead of > 'message to label'. > > Thoughts? > > Rex Kilian > Human-Computer Interaction Institute > Carnegie Mellon University > > > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > Posted from the new ixda.org > http://www.ixda.org/discuss?post=44073 > > > ________________________________________________________________ > 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 > ________________________________________________________________ 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
