UI guidelines for dialog boxes

[Christian Graus]

No, everyone ELSE spells it wrong.... Christian come on all you MS suckups, defend your sugar-daddy now. - Chris Losinger - 11/07/2002

[Nish Nishant]

Christian Graus wrote: Nishant S wrote: 2. Pressing ESCAPE when a dialog box is active will have the same effect as clicking the CANCEL button You get that for free. Only on windows. Even on windows VB developed dialogs dont work this way! My guidelines are for multiple OSs. Java written programs also don't default to dimissing on CANCEL Christian Graus wrote: What is it for ? Another article, or work ? Gosh!!!!!!!!!!!! Not for an article!!! Dis you really think I'd write a theoretical article :eek: I am a member of my company's User Experience and Usability group and I have been assigned the task of preparing a set of guidelines for app development on multiple operating system!!! :zzz:

---

Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]

[Nish Nishant]

Hello James Twine. First of all, thanks for the reply! James R. Twine wrote: 3. On Windows based systems, the dialog will have a Close button [X} in the title bar which will duplicate the behaviour of the CANCEL button This is default behavior. The same goes for (see below). Not for Java and VB developed applications!!! James R. Twine wrote: There are cases where non-modal windows are very useful for data entry. The Properties window in DevStudio is a perfect example: image having to manually dismiss a dialog each time you changed a control's text, ID, or style in the resource editor... Hmmm. I guess I'll have to add a special case clause for that!!! :-( Regards, Nish

---

Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]

[ColinDavies]

Yes I love using

AfxMessageBox("Your computer is toast");

But it is always best ro random seed the appearance of this. Regardz Colin J Davies

Sonork ID 100.9197:Colin

I am sick of fighting with Martin, I think I will ignore his posts from here on in, and spend the time working on articles instead. Christian Graus

[Roger Wright]

I would add that dialog boxes which request permission to perform a function must clearly, in plain language (not meaningless technobabble), explain what will happen when OK is clicked. Additionally, any dialog box presented in response to an exception must include a clear explanation of what application, process, & function caused the error, and provide an understandable description of the nature of the problem encountered. I'm a Frisbeeterian. We believe that when you die your soul is thrown up on the roof, and you can't get it down.

[paulb]

how about this... 10). Modal dialogs should never be nested more than 2 deep. Any more than this just creates confusion (and a mess of nested windows).

[Olli]

Nishant S wrote: 5. Pressing ENTER on a dialog box will have the same effect as clicking on the OK button, except when the focus is on a multi-line edit box Hi Nish, I disagree in that coz I like it more logical, sometimes it's better to behave like the TAB-key.... but I think it depends on the logical situation... Greetings from a strange world....

Olli I feel like I'm diagonally parked in a parallel universe.....
:suss: :rolleyes: :suss:

[Daniel Ferguson]

Nishant S wrote: 6. The size of the dialog box will be such that it will fit within the screen on the lowest target resolution which by default is fixed as 640 x 480. My resultion is 1600x1200 and tiny dialogs with huge (especially multiple-column) lists that must be scrolled to view the entire contents are annoying as hell. All dialogs that would be easier to use if they were resizeable should be. Resizeable dialogs should really be a standard part of the operating system. Another thing is to design dialogs from the point of view of using them, by that I mean they should be designed based on the user's view of the data rather than the programmers view of the data. If I have to spend time to figure out what the programmer who made the dialog was thinking rather than what I want to do, then there is a problem. "You don't have to be a political scientist or a history major to see the 'bigger dick foreign policy' at work. It goes something like this: 'What?! They have bigger dicks? Bomb them!' And of course the bombs and the bullets and the rockets are all shaped like dicks. I don't understand that part of it, but it is part of the equation." -George Carlin

[Nish Nishant]

paulb wrote: 10). Modal dialogs should never be nested more than 2 deep. Any more than this just creates confusion (and a mess of nested windows). Yeah, this is already there in my updated set of guidelines. Strange that we both picked 2 as the maximum depth :-) Nish

---

Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]

[Nish Nishant]

Olli wrote: I disagree in that coz I like it more logical, sometimes it's better to behave like the TAB-key.... but I think it depends on the logical situation... That's a hangover from the DOS days when apps did that. Today only COBOL apps behave that way. The default windows behaviour is to tab on TAB and dismiss on ENTER Nish

---

Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]

[Nish Nishant]

Though there are various implementations of resizable dialogs, none of them are anywhere near perfect. Otherwise the developer must develop separate dialogs, one for each kind of resolution or resolutions. But that'd be a big ask :-( Nish

---

Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]

[Nish Nishant]

Dialog boxes - guidelines • All dialog boxes will have a CANCEL button, and when the user clicks the CANCEL button the dialog will be dismissed without any changes being applied • Pressing ESCAPE when a dialog box is active will have the same effect as clicking the CANCEL button • On Windows based systems, the dialog will have a Close button [X} in the title bar which will duplicate the behaviour of the CANCEL button • All dialog boxes will have an OK button and when the user clicks the OK button, the dialog will be dismissed and all changes will be applied • The user must be made aware of exactly what changes will be applied on clicking OK. This can be done by providing a static text field that explains this bevaviour. • Pressing ENTER on a dialog box will have the same effect as clicking on the OK button, except when the focus is on a multi-line edit box • The size of the dialog box will be such that it will fit within the screen on the lowest target resolution which by default is fixed as 640 x 480. Depending on the target requirements this default may be raised or lowered. • Dialog boxes that accept data entry should be modal. • Where it is required to have a modeless dialog box, only one instance of the dialog box is allowed to be activated at any one time. • Ideally there should not be more than 10 data entry fields on a dialog box, inclusive of edit boxes, combo boxes, list boxes, check boxes and radio buttons. Text fields are not counted. Under special situations where it is absolutely necessary that there will be more than 10 data entry fields in a dialog, they should be arranged in logical groups using group boxes. • The tab order should be sequential and logical. Random jumping of tabs is strictly not allowed. • Dialog controls will always have proper labels. For edit controls that don’t have labels by default, a coherent static text control will be placed to its left. • Dialog boxes should have proper instructions in them, perhaps on the top or the bottom. The user should not have to refer help or documentation to fill in a simple data entry dialog box. • Edit fields should line up on the same vertical line • Static text fields should be left aligned. • Control spacing will be consistent across a dialog box • For dialog boxes that are intended for message showing purposes, and that have no data entry fields, there will be just an OK button. The CANCEL button will be unnecessary in this case and is not to be used. • Dialog box titles will be logical and make clear what the dialog bo

[Olli]

Nishant S wrote: The default windows behaviour is to tab on TAB and dismiss on ENTER I know, you know... but my customers do not really now... When you see them work, they click from edit to edit for example, and not so many are using the keyboard navigation (coz they don't know...)

Olli I feel like I'm diagonally parked in a parallel universe.....
:suss: :rolleyes: :suss:

[Rutger Ellen]

Nishant S wrote: 10). Modal dialogs should never be nested more than 2 deep. Any more than this just creates confusion (and a mess of nested windows). Yeah, this is already there in my updated set of guidelines. Strange that we both picked 2 as the maximum depth Maybe you should add that then a wizard like next next finish set of dialogs should be used ?

[Nnamdi Onyeyiri]

Colin Davies wrote: Unless you have a valid reason for doing so such as the user is using a cracked version, and then you should try to do stuff like this for the sheer hell of it. As can be seen in rule 7 how could u do something like that?

---

:suss: Email: theeclypse@hotmail.com   URL: http://www.onyeyiri.co.uk
:suss:"All programmers are playwrights and all computers are lousy actors."

[Vimal Earnest]

Good points.I like to add a few more Dialogs should support keyboard shortcuts. 1.This means that we can move within a group by using arrow keys. 2.We should be able to select various controls using ALT+key combinations.For this we have to underscore the 'key' letter of the text associated with the control.

[ColinDavies]

1. Only do it randomly 2. Catch the Tab-key message (Pretranslatemessage will do ) 3. Send it to another control at random with SetFocus() Most things are solved simply :-) If you want I'll help you write an App and you can publish it :-) Regardz Colin J Davies

Sonork ID 100.9197:Colin

I am sick of fighting with Martin, I think I will ignore his posts from here on in, and spend the time working on articles instead. Christian Graus

[KaRl]

I suppose you had a look to MS' "Official Guidelines for User Interface Developers and Designers" (msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwue/html/welcome.asp). Even if not perfect, these rules have the advantage to standardize your app with MS ones. For the rule 6, I would also add a parameter about available colour number, like: A dialog box should be fully displayed with a configuration of 640x480 pixels and 16 colors. I agree with all the others. We do not inherit the Earth from our ancestors. We borrow it from our children. Antoine de Saint Exupéry (1900-1944)

[Jeremy Pullicino]

Need to add this one: Dialogs need to fit in a 640x480 screen resolution. "Hey man, Taliban, Tali me Banana."

[Matt Gullett]

Here are some of my general rules. (Note: no rule is totally inflexible.) 1. For dialogs with more than 2 or 3 lines of text or controls, place the control buttons in the lower right of the dialog. (I place them in the lower right for all dialogs now but my data indicates upper right makes no difference for small dialogs.) 2. Also for dialogs with more than 2 or 3 lines place the help button (if any) in the lower left of the dialog. 3. Generally, all text should be left justified for US english display. 4. Button text should be in Upper lower case (ie. Cancel instead of CANCEL). 5. The dialogs title should be in Upper lower case (ie. Warning instead of WARNING) 6. IF the button text or title is in upper case, the other should be also. 7. If possible use Bold. underline and/or italic to emphasise text instead of CAPS. 8. Text in CAPS should be reserved to keu words and phrases only, and never more than 3 words at a time. 9. The group frame is your friend when used wisely. 10. Labels should all have an ending colon or not have the ending colon. Be consistent. 11. If needed, Bold any labels for required fields. If Bold is not avaiable use a leading asterick. 12. Place labels above or to the left of controls they identify, but never below (at least for US English.) 13. For numeric entry fields right justify is best. 14. Avoid the Masked edit control for dates unless changing the date in the control is a rare occurence in which case it should be a picket anyway. 15. Splitters and dialogs don't mix. 16. The tree control is generally evil unless you're software is for other developers especially on dialogs. 17. For dialogs containing lists it is best if the dialog is sizeable. 18. If your dialog is sizable, show the bottom-right chevron so the user knows it's sizable. 19. Edit controls should have a max length specified unless there really is no max length. 20. Multi-line edit control should allow the user to press ENTER to get a new line. Just a few I can think of at 4:30 in the morning.