isabelMar 3, 2025
can you spot the UX issue here?
Show threadAndrew Zonenberg

@isabel This is because the Windows MessageBox() API only gives you a handful of different options for buttons [1] and they picked MB_YESNOCANCEL. It's the obvious lazy dev path forward.

The *correct* solution is to actually put the effort into designing a dedicated dialog with clearly labeled choices, but that's hundreds of lines of code not 1-2.

[1] https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-messagebox

MessageBox function (winuser.h) - Win32 apps

The MessageBox function displays a modal dialog box that contains a system icon, a set of buttons, and a brief application-specific message.

Mar 4, 2025 at 3:23amWeb
Show threadÖlbaumMar 4, 2025

@azonenberg @isabel Yes/No/Cancel shouldn’t even exist, since button labels should be *verbs*, so you have a chance to know what they do without reading the text, and so the text can be an explainer, not a bloody puzzle game.

Also button order and positions are wrong, since the default action should be in the right, Cancel directly to its left, and the dangerous action (“Don’t Save” or in this case “Fry Stuff With 30 kV”) on the left with plenty of space in between.

Show threadÖlbaumMar 4, 2025
@azonenberg @isabel At least that’s what the Windows UI guidelines, which were written by Apple, say.