Cancel - OK
-
Quote:
what Microsoft does throughout Windows(Cancel in bottom right corner, OK to the left of it).
Is just plain wrong. The OK or "moving forward" button should be at the bottom right. The Cancel or "give up and go back" button should be to the left of it similar in action and placement to Forward and Back buttons on browsers - except they are at the top.
- I would love to change the world, but they won’t give me the source code.
This is another line of reasoning that I have seen before that I definitely agree with. Let me just get Uncle Bill on the phone and we can have this whole mess straightened out in no time. ;P
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
For several months now, one of our testers has been pushing to get the OK and Cancel buttons switched in every single dialog in our application (roughly 200 dialogs). His only reasoning for this is that the way we do it (OK in bottom right corner, Cancel to the left of it) is the opposite of what Microsoft does throughout Windows(Cancel in bottom right corner, OK to the left of it). That is his one and only reason. He fails to acknowledge that switching it will annoy the hell out of every single person that uses our software (thousands of people). The next time he brings it up I might punch him in the face. :mad:
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
Colin Mullikin wrote:
Here is an article that better explains my reasoning: Clickety[^]
I see the point you were trying to make now. Keep in mind that only really applies to when learning the software. All of what we're talking about does of course. Anyway... Here's the thing the article does not account for, platform consistency. The whole visual fixation thing only really applies to when the user is first learning the software and also assuming your app is the only one one the planet for the OS installed, which it's not. The eyes and brain will make shortcuts depending on, you guess it, consistency as the user gets used to the computer. In Windows I just know which button is which without even looking for that very reason. Now, here's my take on it in regards to what the guy was trying to say about workflow. Considering the OK button is the button that's used the most, and meant to confirm the whole intent of the dialog even existing in the first place, it should be the focal point of a dialog's action buttons, that's why it's the default with the thick border. The user does not have to worry about Cancel unless something went wrong, which the majority of the time shouldn't happen. Cancel is the bastard stepchild nobody loves. Boo hoo for Cancel, but get out the way because we have work to do. So in regards to workflow only, which the article speaks of,
text > Ok > donemakes more since thantext > Cancel > Ok > donewhen considering the purpose of what the button is even there for. Consistency man. Who cares about what what some guy wrote on his blog.Jeremy Falcon
While I pretty much agree with everything you just said, the key is consistency. We have been consistently doing it this way for over a decade.
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
The real problem occurs if you wipe, then pull up trousers, then wipe again... :~
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
Quote:
what Microsoft does throughout Windows(Cancel in bottom right corner, OK to the left of it).
Is just plain wrong. The OK or "moving forward" button should be at the bottom right. The Cancel or "give up and go back" button should be to the left of it similar in action and placement to Forward and Back buttons on browsers - except they are at the top.
- I would love to change the world, but they won’t give me the source code.
Forogar wrote:
Is just plain wrong. The OK or "moving forward" button should be at the bottom right. The Cancel or "give up and go back" button should be to the left of it similar in action and placement to Forward and Back buttons on browsers - except they are at the top.
And people should fish with a rifle instead of a fishing pole. It's fish hunting season. Point being, just because something is done one way in a different environment doesn't mean it should be done that way everywhere.
Jeremy Falcon
-
Forogar wrote:
Is just plain wrong. The OK or "moving forward" button should be at the bottom right. The Cancel or "give up and go back" button should be to the left of it similar in action and placement to Forward and Back buttons on browsers - except they are at the top.
And people should fish with a rifle instead of a fishing pole. It's fish hunting season. Point being, just because something is done one way in a different environment doesn't mean it should be done that way everywhere.
Jeremy Falcon
-
While I pretty much agree with everything you just said, the key is consistency. We have been consistently doing it this way for over a decade.
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
Colin Mullikin wrote:
We have been consistently doing it this way for over a decade.
I get it, but I don't believe there is every a valid reason for continuing to do something wrong. I realize you got users to deal with that may even not care as much as devs do, but I'd still fix it.
Jeremy Falcon
-
For several months now, one of our testers has been pushing to get the OK and Cancel buttons switched in every single dialog in our application (roughly 200 dialogs). His only reasoning for this is that the way we do it (OK in bottom right corner, Cancel to the left of it) is the opposite of what Microsoft does throughout Windows(Cancel in bottom right corner, OK to the left of it). That is his one and only reason. He fails to acknowledge that switching it will annoy the hell out of every single person that uses our software (thousands of people). The next time he brings it up I might punch him in the face. :mad:
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
Microsoft published a design guide, in the before the before, that suggested putting the OK button on the right was correct and that most user expected that. Then when Microsoft switched to placing OK buttons on the left, the guide mysteriously disappeared. It was a well written research article, to this day I wish I had printed it. My personal opinion is that the confirmation should be in the same location every time and should not float. Placing it on the left makes it float. For example on an OK only dialog the OK button will be in a different place from the OK Button in an OK Cancel Dialog. Long story short, just because Microsoft does something doesn't make it correct. More importantly I agree with your button placement, and furthermore I like using the word furthermore.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost "All users always want Excel" --Ennis Lynch
-
For several months now, one of our testers has been pushing to get the OK and Cancel buttons switched in every single dialog in our application (roughly 200 dialogs). His only reasoning for this is that the way we do it (OK in bottom right corner, Cancel to the left of it) is the opposite of what Microsoft does throughout Windows(Cancel in bottom right corner, OK to the left of it). That is his one and only reason. He fails to acknowledge that switching it will annoy the hell out of every single person that uses our software (thousands of people). The next time he brings it up I might punch him in the face. :mad:
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
I'd be all for leaving it as it is, with cancel selected as the default button. My experience is that users really don't tend to like things moving around, unless they have asked for it. That said don't sweat the small stuff - I know that's way easier said than done. If someone is pushing in such a big way for what amounts to a small change and it does not make sense - make sure you email them explaining why you think it is not such a good idea and let them go ahead with it. That way you have yourself covered if criticism comes your way for the change.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
For several months now, one of our testers has been pushing to get the OK and Cancel buttons switched in every single dialog in our application (roughly 200 dialogs). His only reasoning for this is that the way we do it (OK in bottom right corner, Cancel to the left of it) is the opposite of what Microsoft does throughout Windows(Cancel in bottom right corner, OK to the left of it). That is his one and only reason. He fails to acknowledge that switching it will annoy the hell out of every single person that uses our software (thousands of people). The next time he brings it up I might punch him in the face. :mad:
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
Depends on the structure of your code as to how much work it would be, but you could add a persistent option to the software that allow users to select which standard they want to use: the new and improved Microsoft standard, or the old default way that it has always been. Depending on the option selected, just switch the buttons appropriately. Now your tester is happy, and probably also a good portion of your users who are used to the Microsoft standard.
-NP Never underestimate the creativity of the end-user.
-
I'd be all for leaving it as it is, with cancel selected as the default button. My experience is that users really don't tend to like things moving around, unless they have asked for it. That said don't sweat the small stuff - I know that's way easier said than done. If someone is pushing in such a big way for what amounts to a small change and it does not make sense - make sure you email them explaining why you think it is not such a good idea and let them go ahead with it. That way you have yourself covered if criticism comes your way for the change.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
Don't worry, there has been copious* amounts of discussion on this subject. Everyone knows where everyone else stands on the matter. :laugh: Also, I'm not even the dev that has to deal with making this change. I'm just the one that tends to get into the design debates with this tester. We have had quite a few battles with one another. *Side note: I love using that word.
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
The real problem occurs if you wipe, then pull up trousers, then wipe again... :~
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
That depends whether you wanted to get rid of the stain on the back of your pants, or the wipe is your trousers wiping your sht covered @rse. And member rse just got an email...
I will never again mention that Dalek Dave was the poster of the One Millionth Lounge Post, nor that it was complete drivel.
The console is a black place [taken from Q&A]
How to ask a question -
Wes Aday wrote:
"The button text is wrong". Just figuring that we would know which button he was talking about and what text.
Perhaps you misspelled "OK" on your dialog buttons?
There are only 10 types of people in the world, those who understand binary and those who don't.
-
For several months now, one of our testers has been pushing to get the OK and Cancel buttons switched in every single dialog in our application (roughly 200 dialogs). His only reasoning for this is that the way we do it (OK in bottom right corner, Cancel to the left of it) is the opposite of what Microsoft does throughout Windows(Cancel in bottom right corner, OK to the left of it). That is his one and only reason. He fails to acknowledge that switching it will annoy the hell out of every single person that uses our software (thousands of people). The next time he brings it up I might punch him in the face. :mad:
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
In my expert opinion :), the Cancel button should ALWAYS be on the right, and here's why... Your app undoubtedly has many dialogs, and not all of them have OK and Cancel. I have been writing enterprise apps going on 30 years. The set of dialogs I use contain some of these... - Yes & Cancel - Yes, No, Cancel. - Select & Cancel - Login & Cancel. - Save & Cancel. - Proceed & Cancel. - Connect & Cancel - Rotate, Align, Cancel - Ignore QA & Cancel ... and there are more. See the pattern? Cancel is ALWAYS last. Send your God this book[^]. It was written in book form by MS many moons ago, but the principals still apply. Book form is here[^] Then have him see this[^].
If it's not broken, fix it until it is
-
Depends on the structure of your code as to how much work it would be, but you could add a persistent option to the software that allow users to select which standard they want to use: the new and improved Microsoft standard, or the old default way that it has always been. Depending on the option selected, just switch the buttons appropriately. Now your tester is happy, and probably also a good portion of your users who are used to the Microsoft standard.
-NP Never underestimate the creativity of the end-user.
While I would love for this to be an option, it would require some work. We don't really have an ancestor form with the OK and Cancel that all other forms inherit from. If we did, it would be a nice easy switch, but as it is, the placement of the OK and Cancel buttons has to be switched in roughly 200 forms. We could potentially add a bit of code into each form that would dynamically change the position as you suggest, but I'm not sure it would be worth the work. Also, it would just spawn a new debate of what should be the default setting: the new way or the old way...
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
This particular tester seems to think that he is a God among men when it comes to interfaces... X|
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
Quote:
This particular tester seems to think that he is a God among men when it comes to interfaces...
I think I've met him...and her...many times in my career. I was that idiot, in fact, for the first couple of years of my career. Ask him how much of his pay he will donate to the costs of development and QA for this change.
"Seize the day" - Horace "It's not what he doesn't know that scares me; it's what he knows for sure that just ain't so!" - Will Rogers, said by him about Herbert Hoover
-
To add to what Jeremy and Sander said, how do you know your users are used to it? If they use more than one application on a regular basis, your inconsistency with the established standard could already be irritating them - just nobody told you because they thought it "was just them". Your QA guy has a point: standards are there for a reason - consistency!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
In my experience if the form elements, like button, have some visual significance it does not matter where they are on the form. The eye goes after what it sees... However if the design is flat (what is very 'cool' today) the standard place is a must-have for form elements.
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
For several months now, one of our testers has been pushing to get the OK and Cancel buttons switched in every single dialog in our application (roughly 200 dialogs). His only reasoning for this is that the way we do it (OK in bottom right corner, Cancel to the left of it) is the opposite of what Microsoft does throughout Windows(Cancel in bottom right corner, OK to the left of it). That is his one and only reason. He fails to acknowledge that switching it will annoy the hell out of every single person that uses our software (thousands of people). The next time he brings it up I might punch him in the face. :mad:
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
What about letting users configure it themselves? A simple routine to set the button text and dialog return value for all OK/Cancel buttons would do the trick. That way older users could keep doing things the way they are comfortable with, while new users could do things the "Microsoft Way" if they want. Or you might even get rid of the Cancel buttons. I never saw much use in them myself. The "X" in the upper right corner can be used for the same functionality. I suppose it might make some users more secure having a specific button for abandoning changes, though, just so they could be sure their exit is done in a controlled manner. Although you can code the X to do exactly the same as a Cancel button, it might seem more unsafe to users.
-
Colin Mullikin wrote:
That is his one and only reason.
And it's a valid reason.
Colin Mullikin wrote:
He fails to acknowledge that switching it will annoy the hell out of every single person that uses our software (thousands of people).
It probably annoyed them when y'all did it backwards to start with. Can always annoy them again. I've studied UI, and the whole reasoning behind doing something like
Cancel | OKis completely invalidated by never changing its order. In fact, to be consistent with the premise of it, you should change it randomly (ie to force users to read the message). Otherwise it just shows a complete lack of disregard for standards and poor UI design.Jeremy Falcon
Quote:
I've studied UI, and the whole reasoning behind doing something like Cancel | OK is completely invalidated by never changing its order.
Really? You've "studied UI"?? Add to your studies that many if not most of these OK/Cancel buttons respond to Enter for OK and Escape for Cancel. Man does not compute by mouse alone, and neither should a UI expert. Talk about ivory towers...I've seen what you suggest in actual implementation for truly critical application paths, and it has its place there, but for general use in all applications your user base would rise up in arms and depose you for a less educated but more practical developer. BTW, as part of my Master's Degree in Computer Science, I took the User Interface Seminar, so I'm familiar with the principles you expose. Many of them fail miserably in general practice because they interfere with getting things done as quickly as humanly posssible for the least cost, which are principles from another discipline entirely called BUSINESS.
"Seize the day" - Horace "It's not what he doesn't know that scares me; it's what he knows for sure that just ain't so!" - Will Rogers, said by him about Herbert Hoover
-
He might annoy you and all the other devs, but he DOES have a point... I've dealt with customers who wanted me to change my software because it was not compliant with the Microsoft standard (small things like the order of OK and Cancel, an icon etc.). I'm now pretty keen on keeping things consistent with the OS I'm aiming at and, when there's no standard yet, keeping things consistent within my application. Perhaps now your customers are used to it it's not a good idea to change it though... Although new customers may benefit from it.
It's an OO world.
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}Quote:
Perhaps now your customers are used to it it's not a good idea to change it though... Although new customers may benefit from it.
Cost versus benefits...if your current user base is very small compared to the new user base, and your new user base is more likely to purchase your product if you change, then it may make sense. These changes do not come for free.
"Seize the day" - Horace "It's not what he doesn't know that scares me; it's what he knows for sure that just ain't so!" - Will Rogers, said by him about Herbert Hoover
