Tag Info

Hot answers tagged

25

Not according to Microsoft. Use title-style capitalization, without ending punctuation. Source: Microsoft Guidelines for Windows, section about error messages.


22

I would say that this often leads to an unwanted drag and drop action. What if this window for example has a small scrollbar, you want to scroll to the bottom of the page and you accidentally miss the scrollbar? You would drag the window down and you might need to reverse this action. Why is it uncommon that windows can be moved by clicking anyway in the ...


16

My answer would be to synopsis the question of the modal form, so with the question being: You are leaving the question with unsaved changes The title would be: "Unsaved Changes" It's a pattern I've seen and used regularly, it's brief and informative.


13

The title bar isn't always the only spot to that can be used to drag the window, (these days some windows can be dragged by parts of their background, but it's rare) but it's the oldest and most established and common convention. It originated in the early WIMP UIs, the Smalltalk systems from the 70s and 80s. If you study the way the above windows were ...


12

This is actually not always true. In some cases the default behavior of most apps would be to allow to drag windows by empty space. An example is KDE. See the screenshot: KDE's default Oxygen widget style has window decoration visually merged with window contents. Thus, to make feel match look, the theme also by default allows to drag windows from all ...


10

This area is normally giving you information on the type of question being asked (at least in my experience), so the question mark feels like the dialog is questioning itself. I'm a "Save Changes" dialog... or am I?


10

The Windows OS provides the (optional) title bar and control box, as well as a mechanism for OS users to organize their application windows (re-positioning, minimizing, maximizing, closing). From the perspective of the Windows OS, the title bar is the user's API for these operations. Everything else in the window is "content" that is under the control of ...


10

Exporting data can be more time consuming Ultimately it depends on how your users feel about it but exporting data requires users to think more and can add friction to their work flow. If I could only choose one option or the other I would go with option 1, however, export to Excel sounds like a very useful function so consider the following example. Show ...


8

Great question. I've been thinking a lot about "confirmless deletes" because of a behavioral issue with models that is outlined here. In short, most users actually intend to delete an item when they initiate the interaction, so throwing up a traditional confirmation is annoying most of the time. I totally agree with Lauren's answer on the basic ...


7

In general, I use the following guidelines for using modals: Is it focused? Every time you throw a modal in front of a user, you're disrupting their workflow. Disruption isn't always bad. Sometimes that's what you want. But you have to realize you're doing that and use it for your benefit. Items within a modal should self-contained. A good rule of thumb is ...


6

When deciding between a modal and inline entry, consider what is communicated to the user by your choice: Inline Blank Entry "You're going to be doing this a lot, so we don't want it to be a big deal." "Don't worry too much, this is easy to fix if you make a mistake." "We expect you to enter multiple items." Modal Dialog "Please focus. This is too ...


6

A lot of the challenge you're dealing with stems from the complexity of communicating and managing the relationship between the two windows (form and calculator). Ultimately, it looks like the calculator is there to assist with the form, so you may want to consider removing the "two windows" part of the problem altogether. Just have the calculator slide ...


5

Yes, there is extensive research on this question available in the literature on usable security, and they have found that users do indeed become jaded. This is an important challenge for making security usable: sometimes developers think, if in doubt, just throw in another warning dialog; but the research literature shows that this is a bad idea. ...


5

Microsoft conducted a lot of testing into the User Account Control (UAC) between Windows Vista (when it was introduced) and Windows 7. They have a post about this on their msdn blogs: We have learned from our customers participating in the Customer Experience Improvement Program, Windows Feedback Panel, user surveys, user in field testing, and in house ...


5

Dialog boxes are needed. In the old HCI thinking, a user interface is essentially a dialog between a human, and a computer. However, handling of the dialog boxes can become habitual. The typical example is Word or any similar document editor: when you close an unsaved document, usually, you don't want to save it. In those exceptional times when you actually ...


5

It very much depends on the type of your application the operation it is doing. Ideally user should always be in control, but there are situations when you will want to keep control when you are making critical changes. Firstly, you must inform user that a following operation might take X amount of time and that she may not be able to use the system. ...


4

In my experience, modal windows are best used to present clear interactions that the user either: needs to do (e.g. resolve an alert) has chosen to do (e.g. open a photo gallery). Resolving that interaction should close the modal, and there should already be a control in place that does that. This is because modal windows interrupt the user flow and ...


4

Modal windows are quite common nowadays so the user might not but surprised to see something like that appear. The content of the modal window is more important than the pattern itself. If the content is an action, it is a common pattern to use ellipsis (aka suspension points). If the content is just information and long, you should just use a simple ...


4

Take a look at this UX/Design guideline from Google about Confirming and Acknowledging: https://developer.android.com/design/patterns/confirming-acknowledging.html Although the guideline is for mobile applications, the principle and flowchart highlighted in the guideline can help you and your team decide when and when not to use alerts and confirm dialog.


4

No never. Adding a second modal dialog over the first one is the equivalent of using pop-up window over pop-up window (and there's a good reason they where blocked in the browser and soon deprecated in web design). Instead try to guide your users through a modal dialog wizard with clear interface of what to expect next. User feel comfortable and trust the ...


4

You'll find that nearly without exception, question form in modals is little appropriate. On content vs interaction Probably to core duality in all interfaces is the that of content and interaction. Respectively, what you can see and what you can do. Cognitively, these are mapped to (so to speak) two cognitive processes - interpretation and action, which ...


4

The 1990's called! Please return its cascading message boxes! Alerting system are extremely complex and difficult to get right. They require subtlety in one case, while demanding you slap the user in the face the next. If you fail to get it right you either cry wolf every time (your current design is doing this) or hide them in the corner. You should ...


4

While this answer may not relate to the titled question, it does relate to your particular case. I find the modal dialog itself very awkward, regardless of the color of the buttons. When a user enters text into the input field, the green add button (+) appears. Clicking this button enables the submit button (Update) and allows the user to add more ...


4

Your dialog actually has three buttons - cancel, assemble, load into simulator. The primary button is "load into simulator", because that's the one that lets you close the dialog and proceed. By only displaying it after the user has generated valid code you're breaking the process down into steps, basically making this a kind of wizard, but not supporting it ...


4

This is one of those times where you have to balance what the user wants against business objectives. Not showing the newsletter lightbox is better for UX (no real question about that), but it's worse at achieving the business objectives. What you have to weigh up is how important those business objectives are against whether you're willing to harm the UX ...


4

Severity and recoverability of the action can help guide the style you use. Also the platform you're on. Platform standards also playing a role. Dialog vs. Undo This was discussed in the following Q&A. When dialogs vs. undos make sense: Deletion: Confirm or Undo? Which is the better option and why? Slide to Delete Gestures on mobile devices ...


4

If there is no safe way for the user to leave the process then you really should make them wait until it is complete. Leaving them with a faulty system is potentially more damaging to the software's reputation than making them wait for an extra 20 minutes for a correct and perfect instal. However, I assume that they've gone through some sort of process to ...


3

Arguments of the appropriateness of modal windows aside (because I don't think we have enough context for that from your question), I think your reasoning for why this is a good idea is sound. Some users rely very heavily on the back button: The Back button is the lifeline of the Web user and the second-most used navigation feature (after following ...


3

Inline not Modal Inline edit is to be preferred at all times. The user keeps context, have the ability to use information related and narrow to the edit and the user don’t have to focus on a new UI. It is the same, simple, easy and straightforward process where the flow of work can be kept. Modal dialogue breaks the users’ context and it takes time for the ...


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 ...



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