Copier Lighten / Darken Label Confusion

What happens when I press the left button?

The region function label "Lighten / Darken" almost looks like labeling for the buttons that change the parameter. But, they are reversed relative to the action that takes place when the button is pressed.

Maybe simply "Darken / Lighten" ?

What's my options?

Apple's iOS is generally excellent, occasionally sublime, but it can be a co-conspirator in a user experience failure:

"Would I like to connect to the server anyway?" I think "not!" But how do I bail out? An experimental tap outside the box doesn't clear it. So if I tap on "OK", my only choice, who's responsible for placing my confidential information at risk?

Behind the scenes, what's happening is that iOS is asked to make a (probably) HTTP connection to evernote's server to synchronize my notebook. As you can tell from the orange airplane icon (questionable UX), the 3G radio is shut off and the connection is attempted via WiFi. Fine, but it happens that I'm at a public hot spot that requires a log in before a connection is made to my intended server. Apple's iOS asks for a security certificate and the log in screen doesn't supply the expected credentials. The fact that no certificate or one from the wrong entity does not get noted to the user. That would be a hint that a common action - the need to log in to a hot spot - is needed to complete evernote's goal. How about a message that states that a connection failed, it will be tried again later?

I haven't programmed in an iOS environment but I suspect that this common situation could be detected and a more useful message, with reasonable options, could be presented.
---
Tosh

User eXperience - Fail, why?

This is a collection of examples of gross failures of a programmer to communicate - inform, direct the user as to what has happened and what options are available from this point.
One of my favorite examples comes from Novell:

G: is already connected to \\BRD-SRV1\PROJ1.

Do you want to connect G: to \\brd-srv1\proj1 instead?

 

I get that there was a problem. I doubt that it was really a case problem (it's MS Windows XP, after all.) But what are my options? Try again? Abandon what I wanted to do - perhaps just walk away?

A useful message might have told me the real reason the original drive mapping operation failed. Even if the dialog explained that an unknown error happened and ask if I want it to try again, it would be useful. Of course if another failure happens, I expect a more useful explanation.

---

Tosh