New answers tagged checkboxes
To decrease the upfront cognitive load, and guide the user on optimal course, I would recommend the initial upload dialog not having a prompt about file saving at all. Rather have the confirmation message explain system state, and allow for fine grained control if required. download bmml source – Wireframes created with Balsamiq Mockups
There's only one idea that's clearly different from the other ones, B. I often too, overlook the checkbox entirely (not that I really miss it, with chrome storing all my passwords). It's the most common design pattern yet, to me (and you), it just doesn't feel like good UX. As I mentioned, my choice would be B. Checkboxes are easy to miss as they might not ...
EDIT: Check the end for the final verdict, and my favorite option. If it doesn't impact site performance or otherwise negatively influence anything on your site, and you're not worried about server space, you could simply have the checkbox with a default checked state/attribute, and the user would have to uncheck the box in order for the file not to be ...
Those are all good options. How about just "Save" and on click of Save, show user a dialog box to save the files for future use (with remember this option). Especially in a mobile experience, user would rather have a dialog than see multiple buttons on the same page that he most likely will not notice.
I don't think you should base UX on what pleases you. What will most users understand? The way Microsoft does it is what most users will understand. I think a gray check is more intuitive but I went with the way Microsoft does it. I am responsible for an app that is in an industry that is not computer savvy and have these battles with marketing all the ...
I don't know the full context of your situation, but I think you have more of a wording issue. As you state, there are 4 states. So using yes/no doesn't make sense at all. Sounds like your for initial states should be set via radio buttons as: ( ) Has a discrete graphics card ( ) Has a integrated graphics card ( ) Does not have a graphics card ( ) ...
What about providing a vertical slider to the right of you list that can snap to one of the 4 distinct states?
Well, you have the answer in your question - you lined up the answers like a bullet list. Do the same, but with radio buttons. They are often the best option when there are few options, but one (and only one) have to be selected.
If space is a consideration, you could also make a second step with a popup, or a second page. The first page consisting of a single Yes/No Choice, for example two buttons. If the user chooses No, he will get a second page with the checkboxes to choose Options. If you are at all concerned with people using touchscreens, this should be the best options, ...
Use either Responsive Disclosure or Responsive Enabling depending upon the standards in the format you're working in. Responsive Disclosure would mean first showing a radio button like this... download bmml source – Wireframes created with Balsamiq Mockups ...and then revealing the additional option in the whitespace if the user selects no, ...
I don't think either of these is the best option. Do you have to go with one drop down? I would prefer to see two. The first would display and the second would be hidden until the user selected either yes or no from the first. Once selected the second would display with the appropriate options.
The following can be an option to present this scenario: Clicking a cell in calendar, a menu displays the available options. You can select the required options and click anywhere to close the menu. The cell displays the number of selections.
Provide an additional checkbox to select all results. This way you'll only need one button. Furthermore the Select All checkbox is a control used by many websites (e.g. GMail, GWT, etc.) I strongly recommend to use only one button, as the action (send e-mail) remains the same, it's only the input that changes.
Top 50 recent answers are included