>>>We don't know anything about his interface. Maybe He wanted left keyboard just typing and don't want let call button with invalid keyboard strikes or something else...
>>
>>Exactly! When we don't know enough about the UI why is it that the first reply is always, "Don't. Its not standard practice. Microsoft guidelines says blah, blah, blah." If it was an absolute no no to not have this functionality (along with flashing text - another one that brings out the same response) then why does the tool (VFP, etc.) allow for programmers to do so?
>
>The standard practices are what the Redmondians recommend, not necessarily what they do. Just look around any of their app (or the OS itself) and you will find a bunch of things you can't do without a mouse. Anyone know a keyboard combination to (right)click items in the tray?
>
>As for the flashing, it is extremely annoying and I haven't found anyone who liked to watch it. I know a few guys who liked to write flashing screens back in the DOS days, when they thought it was cool. And Fox still has it for backward compatibility. And perhaps a couple of urgent cases when you may really need it. But then there are so many ways to write awful GUI, flashing or not.

Agreed (mostly). However, no matter how much you may dislike flashing text, I'm am certain that there is an appropriate time and situation where a developer would want to use it and if they didn't have that ability it sure would suck. For example, think of an application aimed towards kids. Say a simple math game where if they got the answer correct, it would, God forbid, FLASH green!!!!