>>>>No, these controls depend our other internal libraries. but you're a good developer. Really easy things...
>>>>Create a container for on screen keyboard, do not put buttons, just put key pictures and catch click event so your textbox controls don't loose their focus...
>>>>Others so easy too...
>>>
>>>The same trick can be done with regular buttons if you put your action code not in .click() but in .when(). Your code does what it needs to do, then returns .f. and your buttons never get focus.
>>
>>But why should it not get focus?? Suppose I use command buttons and do a getfocus to a hidden and readonly text field in its click()?!
>
>There are such scenarios. For instance, I have an editbox with several buttons that do things to its .value, and I don't want the code to move my insertion point. I want it to behave like the usual formatting buttons in text processing (even though they don't do the same thing at all).
>
>The technique with the invisible textbox is an old one, saw it first in an VFE 5, IIRC, but it's possible that it was there since some of earlier versions of Codebook. And even that doesn't require the commandbutton to gain focus - actually if it was on a toolbar it never would - and the current control losing focus was required for proper save, otherwise its .value wouldn't get copied into its .controlsource, so the focus had to be shifted.
>
>IOW, even though I don't like my code to depend on scenarios, they do exist and dictate the behavior.

You don't like scenarios for you code pieces? You mean you don't like to have a framework?