Le 30 janv. 08 à 16:40 soir, Joe Strout a écrit:
> On Jan 30, 2008, at 8:33 AM, Norman Palardy wrote:
>
>> 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.
>
> With all the typing that's gone into this thread, it seems like we
> could have solved it by now. The Window.KeyDown event should get the
> Tab (or Shift-Tab) key before it's used to change the focus. So, we
> could make a Window subclass (TabManagedWindow) which intercepts that
> keypress, and moves the focus in whatever custom way you choose --
> perhaps by looking at the ControlOrder plus a set of non-tabbed-into
> controls you set up in the Open event.
>
> Not quite as elegant as having it built-in, but not that big a deal,
> either. If you have some unusual data-entry app that needs a
> nonstandard tab order, this would let you do it.
Do you know how we can access wether any control or just edit fields
and listboxes can have the focus on Mac OS X? (you can choose either
in system preferences).
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|