Yes, the design is awful. There's no indication that you're being asked for your password. I had to come here and read this before I could work out how to change my email address.

- Pfft. Coddled kids. In my day, we used to telnet to port 80, then render the page with pencil and paper-- and that's the way we liked it! - Pshaw! Youngster. Your UID barely fits inside 16 bits. In _my_ day we had to whistle the 1's and 0's through an acoustic coupler! Tools that support "all of UTF-8 as long as it starts with ASCII" and tools that cannot handle these three [BOM] bytes at all are not really supporting UTF-8. - Michael Kaplan

Am I the only one who's noticed this? Has it only happened to me? It seems that, if you have a multiline edit in an XP-themed app (i.e., an app using ComCtl32 v.6), the word wrap does not take into account accented characters and breaks on them. So, for example, if I write "error de aplicación" in Spanish and the edit happens to want to break around the end of the last word, it might break immediately after the "ó". I would be interested to see if anyone's seen this because I've fixed it by writing a callback to handle word wrap, modified from some ancient code from a Microsoft example. This has, in turn, highlighted another bug, this time in the definition of the first parameter received by EditWordBreakProc. It might be worth turning this into an article, but am I the only one seeing this problem?

I don't know whether you're still out there, but if you are: look up EditWordBreakProc in MSDN. You can define a callback which sets up a different word wrap routine for an edit. I might be posting an article on this since I think there's a bug with the word wrap in XP-themed edits.