Tag Info

Hot answers tagged

5

I'm going to be the wet blanket and suggest that there may not be a big benefit. The fact that these are being used more often is more about changes in technology. We can do it this way now, so let's do it this way. Yes, drag-and-drop is not a new concept. It's been part of our systems GUIs for 4 decades. But note that the process of uploading a file via ...


4

The overall usefulness here all depends on what files you want to upload, how your workflow is and how you organize them. Scenario 1 : You know where your stuff is You know exactly which files you want to upload, how they are named and in what folder they are located. Navigating to them in an explorer window and drag/dropping them will need ...


4

In many UIs, you can input a number directly in a spin box without using the arrows. Taking this fact into account, I think that you should use a spin box only when it makes sense for the user to change the value using the arrows instead of inputing directly a new value. In my opinion, using the arrows makes sense only when you need to increment/decrement a ...


3

Use spin boxes when the value being entered is a numerical value within a range, and don't use them when the number instead represents an identity (e.g. port number). Especially consider using spin boxes if the value is a numerical value where you want to encourage particular increments (e.g. thousands)


3

The only time I can think of when no close button should be there is when "Cancel" action is not acceptable, e.g. the user must make a choice. This is often connected to popups that isn't caused by user action. For example, the system must be restarted and asks the user when the system should reboot. "Now", "In an hour" etc. Letting the user close that ...


3

It all depends on the alert that is being provided to the user. If it is an alert with regards to purchasing and item (i.e. In-App Purchases) usually the "No" is highlighted as to prevent accidental purchases. However, when it comes to cases such as connecting social accounts or opening a link in safari, "yes" should be highlighted because of the likely ...


3

Modal windows opening up other modal windows is a recipe for disaster. An approach you should consider has two components; a form editor and form navigation. If the forms are sequential in nature or nested, then a navigational component, similar to mileposts will help the user know where they are in the sequence, and facilitate navigation to previous ...


3

The placement of the OK button really depends on the content of the modal. If you tend to use them for forms, a left justified button may be best. As forms are usually left justified it is easiest for users to go down in a straight line. A user's eyes are likely not to leave the left side of the modal often. However for shorter modals that may not have ...


3

Drag and drop save much time because folder with working files are often opened and it's faster to drag it directly to website. I do it little bit faster: Alt tab from browser to folder Click and hold document icon Alt tab to your browser RELEASE!


3

As it is going to to be used by non-professionals, I would suggest using swatches in the first place. It's a great starting point, often offering proper balance between choice and usability for such use. As a second level (only for situations, where swatches are not enough for user) you can indeed provide an optional color picker. You have following options ...


2

Drag drop can be useful in various cases e.g. If folder with file is already open - saves you time of browsing to the correct location from the open file dialog. You can drag multiple files in one go. You can drag items from open apps e.g. drag an image from an image editing application or from an open browser window without even saving the image. In some ...


2

A Dropdown with just two options isn't the right way to go consider displaying both the options with radio buttons. Using tabs in a wizard wouldn't be appropriate. Consider something like this . It will be a better to convert the tab into one additional step.


2

A wizard with tabs? Wizards and tabs should be mutually exclusive. As it says on page 179 of the Windows 7 User Experience Interaction Guidelines, you shouldn’t use tabs if the controls on one tab are dependent on the settings of another. The user should have one decision for each page of a wizard –there never should be so many controls that you need tabs. ...


1

I want to start of by saying that I loath modals. I do know that there are certainly scenarios where they are good and necessary, but I really don't like them on principal. That being said, some of the examples given, I would argue, do not justify the disabling of the close button. A close button is a very known and comfortable escape hatch. Depending on ...


1

Personally, I think Microsoft's guideline makes little sense. A typical dialog requesting a decision from the user give buttons for all of the possible actions to take at that point (ok/cancel, yes/no, save/don't save/cancel). On most dialogs, the close button doesn't give the user additional "control"; it just provides a duplicate way to perform an ...


1

Considering the user cannot navigate to the second tab, keep it disabled. When conditions to enable it are met, enable it and provide a fade-in animation such that the user notices the change. Keep it simple! :)


1

Surfacing new features and 'discoverability' in general are major UX challenges. Don't expect a change log (or any other approach) to completely handle this for you. Users can and will ignore even outrageous modal dialogs. As a general goal, you should strive to make new features naturally apparent to users... sometimes easier said than done. For a ...


1

Removing the [X] button should be avoided at all costs since it is the go to button if you don't know what to do and want to cancel your actions. That said I have had to make a few of them in the past. The reason was that we were building a new UI on a very old piece of software. On 1 or 2 occasions the software needed a response from the user in such a way ...


1

Have you tested the functionality with your User? It is not difficult or very time-consuming to locate and garner files using the OS search functions and copy and paste them into an appropriate folder. I would be very upset if I had to pogo stick in and out of your upload dialog 20 times to populate a photo gallery.


1

Actually the accepted answer does not show one main reason why it has been made this way. More than visual perception, putting a fixed bar at the bottom of a modal popup which has actions (like "OK" button in your examples) will let the user see the possible actions even if the content section is too big to fit in a small screen -->There is a scrollbar. ...


1

My theory is that it conveniently simulates the already learned drag and drop convention on the desktop. Opening a separate File browser can usually disorient the user because they'll have to relocate the file again. Imagine... You save a file to the desktop. You locate the file on the desktop. You drag the file to the browser. Simple! With a file ...


1

Drag and drop for file actions is common across the wider operating system environment, the file upload button is typically a control specific to browsers, and therefore when dealing with file based operations isolates them from the wider operating and UX environment that they inhabit, thereby potentially creating a break from the global UX. Implementing ...


1

If I am reading the description correctly, a person cannot type a different number into the text field that is in focus? If that is the case, that should be changed as placing that field in focus implies that the user doesn't have to use their mouse. One idea would be to allow the user to type whatever value they want into the field, and then show updated ...



Only top voted, non community-wiki answers of a minimum length are eligible