Behavior of CommandBarEdit.SetFocus()

I'm not quite sure the behavior I'm getting from the SetFocus() method of a CommandBarEdit control is exactly what should be happening.

The first thing our application does after launching is require a user to sign in. Following good UI practices - since we know that the Username field will need focus, it would be nice for us to do that automatically (think My Yahoo! sign in... 1) launch page 2) type away)

The problem:



It seems that the control is getting focus, but there is no visible caret and typing has no effect. Hitting the tab key once brings us to the desired state, but should that be necessary?

Issue #2 (this is more like a question...)

Is there any control over what toolbar items are shown when the window is not wide enough to show all of them? You can see in the following screenshot that the 'Password' field has been dropped. Since this field is absolutely necessary, it would be nice if I could give it higher priority than the simple tool shortcuts in the toolbar to the left.



See what I mean?

If anyone could advise on either of these issues, it would be greatly appreciated.

Regards ~ jp

Thanks Oleg -

Both solutions work nicely. You are like the Gary Kasparov of programming

The CommandBarKeyDown Event... reference docs don't mention what the behavior of that is for CommanBarEdit / CommandBarComboBox, but it appears to be fired for at least Tab (keyCode = 9) or Enter (keyCode = 13).

Why doesn't this work for the alphanumeric keyCodes? I'd like to prevent the user from using certain keys (i.e. spacebar in password).

Is this possible?

Regards ~ jp