Which requires me to press “OK” in order to proceed with my quest of wading through a morning’s list of messages while waiting for the car in front of me to move another inch through morning traffic jam.

In order to avoid the alert dialog / message, I would suggest to insert the new message into my list of messages, probably marked with a special badge or color in order to let the user know that the message was sent.

Lesson to be learned:

Avoid alerts at all cost. They get in the way of the user. Most of the time, users don’t read them, anyway. There’s almost always a way to achieve same goal without an alert dialog.

(…stepping down from soapbox)

• Preamble
• The Humble Dialog Box
• Supervising Controller
• Passive View
• Presentation Model
• View to Presenter Communication
• Answering some questions
• What's the Model?
• Assigning Responsibilities in a Model View Presenter Architecture
• Domain Centric Validation with the Notification Pattern
• Unit Testing the UI with NUnitForms
• Event Aggregator

Plus, as a bonus, you will notice that Jeremy is not afraid of using really long function names:
void CloseTheScreenWhenTheScreenIsDirtyAndTheUserDecidesNOTToDiscardTheChanges()
And I’m mentioning this not to make fun of Jeremy.

This highlights a style of software design…driven by a desire for consensus and for “Making Everybody Happy,” but it’s based on the misconceived notion that lots of choices make people happy, which we really need to rethink.