OpenEuphoria

RE: Trapping the TAB key

• Posted by Derek Parnell <ddparnell at bigpond.com> May 06, 2002
• 382 views

Jonas  Temple wrote:
> Derek,
> 
> I'm not sure I understand the intent of this fuction.  Does this mean 
> that there are NO tab key handling in win32lib or just that win32lib 
> doesn't perform it's normal handling of the tab key?
> 
> Just confused...sorry.

The routine setTabCodes() is designed to let the application define 
exactly which keys can be used to 'tab' between controls. By default it 
is the VK_TAB (ascii 9) key.

The way the library works is that for each key press detected by 
win32lib, it checks it against the list of 'tabbing' keys, and if it 
matches one of them, win32lib then performs a 'tab' operation otherwise 
the key is passed onto the application.

So by setting the list to 0, just means that no key will ever match so 
win32lib doesn't do any 'tabbing' operations and all keys will be passed 
onto the applications.

For example, if you set the 'tab' key to F8, then the normal TAB key is 
passed to the application and F8 causes win32lib to do 'tabbing' 
operations.

There is a related routine, setTabEnabled(id, flag), that allows the 
application to define how a control participates in the tabbing 
operation. In other words, you can set some controls to ignore the 'tab' 
key (but it still responds to Ctrl-'tab').

I've just noticed that these two routines have not been documented yet. 
I'll fix that up immediately.


> Also, in reference to the ES_NUMERIC, it works fine on Win95/98 but 
> doesn't seem to work on Win2000 Pro.  Does that help?

Not really  I run Win Me at home, Win2000 at the office and Win98 on 
the laptop.  Unfortunately I'm not near any of these right now so I'll 
see what else I can discover about the style flag.

---------
Derek.