On 30-Jan-08, at 12:22 AM, Tom Benson wrote:
> I've done a lot of high volume data entry work, and couldn't agree
> more, but...
>
> There is a very simple work around for this... it's a bit hackish but
> it works well.....
>
> Each Window has A Dictionary property called CanGetFocus
>
> In each control's open event, I add a dictionary entry to the
> dictionary with a reference to the control as the key and a boolean
> value.
>
> e.g.
>
> CanGetFocus.Value(me) = False
>
>
> Than in the gotFocus event of that control
>
> If not CanGetFocus(me) then
> DeclareLib.PressKey(DeclareLib.PressKey.kTab)
>
>
> PressKey is a cross platform function that calls a system level
> declare to simulate a press of the Tab Key...
>
> This skips focus of the control and moves it onto the next control in
> the chain which accepts focus.. and the best part is you can get and
> set this ability at runtime by altering the dictionary entry...
The only downside is this is an all or nothing kind of solution.
What's needed is a way to designate that a tab into a control should
skip the control but if you click on the control it can get focus.
There might be a means to use your mechanism to detect this case and
behave accordingly.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|