New answers tagged

1

The most straightforward approach for the user is to keep the behavior when clicking a checkbox and clicking a row independent and internally consistent. In other words, clicking the checkbox should always select/deselect the row and clicking the row should always expand/collapse the "important info" content. Therefore, if the user has checked a row via the ...


0

I wouldn't show nothing and prevent the user from continuing - That will only create confusion and frustrate the user. The best method for handling user errors is preventing them in the first place. You can't always do this entirely but usually there is something you can do, build some logic in your application that means the user won't have to deal with ...


3

Train your users Start by letting your users know how to use the system, and define some common notices. For example: Explain the process Now, you can tell them that if they do something unexpected, they won't be able to do the task. You can also add a right click notice to explain EXACTLY what is wrong (and of course, tell them "right click on element for ...


0

Perhaps a div at the top or bottom that expands when an error has been detected, and collapses when a new selection is made or a close button has been pushed? Animation, color choice, and sizing would be key to ensure that it's noticed, but isn't overly obtrusive.


2

Here are some options to reduce cognitive load and make the task easier: Shorten your descriptions. 200 symbols * 19 options = 3800 symbols, which is roughly A4 sheet, full of text. Looks crazy. Substitute long description with short labels. For repetitive users this is OK, for the new ones provide some help/guide. E.g. "Home", "Professional", ...


3

Considering your design layout, I really think the best option is to use either checkboxes or radio buttons (depending on whether the user can select more than one option or not). Below is a quick mockup of what I mean: However, if you have a large number of options, this could prove to be problematic. In that case, I would consider having your Section C ...


1

In most (if not all) modern browsers and Operating Systems the menu of a dropdown is a separate (but not independent) object from the trigger. download bmml source – Wireframes created with Balsamiq Mockups This means that the text on the trigger can be safely truncated while the contents of the menu remain full length - Effectively showing the ...


1

It's difficult to give a complete answer without understanding the requirements, but there is a (potentially) existing pattern in stock Android - the data usage tab. User selects the upper maximum by dragging the x-axis line up and down to set the maximum. Downside is it may not give you the required precision to select the value - but you may be able to ...


1

If you only have room for one object, then you could use interpret a string like "unlimited" or "Infinite". Make sure you check for all possible input possibilities though! Capitalizations, different words, the number 0 is often used. As you can see, this is messy. A much safer and gradual option would be to have a toggle and a textbox (or other selector). ...



Top 50 recent answers are included