What’s wrong with this code, part 26 – the answer

re: What’s wrong with this code, part 26 – the answer

Alexandre Grigoriev — Mon, 29 Jun 2009 23:51:05 GMT

Under "things you should not do" I'd also add "playing Ding in response to an unknown key in a server UI utility".

re: What’s wrong with this code, part 26 – the answer

tb — Tue, 30 Jun 2009 14:45:29 GMT

Also filed under "reasons to not reinvent the wheel." There was a perfectly good async call already.

Start thinking in microseconds, and a second becomes an eternity.

re: What’s wrong with this code, part 26 – the answer

Maurits — Tue, 30 Jun 2009 16:36:20 GMT

"Ding" in response to an unknown key is quite common; numeric-only text inputs do it, for example.

Open Notepad;

Ctrl-G to pop up the "go to line number" box;

press a non-numeric key ("A")

Ding!

re: What’s wrong with this code, part 26 – the answer

Alexandre Grigoriev — Tue, 30 Jun 2009 16:48:21 GMT

Maurits,

Notepad is quite old, and was designed for general audience.

On the other hand, the server utility we're discussing doesn't need those bells and whistles.

re: What’s wrong with this code, part 26 – the answer

jcoehoorn — Tue, 30 Jun 2009 20:11:02 GMT

As a followup then, when would you ever want to use SND_SYNC? Or, put another way, what are the potential costs of this fix?

re: What’s wrong with this code, part 26 – the answer

Ben Voigt [C++ MVP] — Wed, 01 Jul 2009 00:00:06 GMT

I guess as a specific case of "long running items", don't do any UI work whatsoever from threadpool threads, right? At most you should Post (not Send) a message to a window or thread whose message queue has already been created (you know because the thread created its message queue before starting the work item).