Leaving an EDITTABLE without the mouse (OpenInsight Specific)
At 17 OCT 1997 06:35:22AM Peter Richards wrote:
Most clients have come from DOS based applications where ENTER or TAB was used to go to the next 'control'. Now with some of the OI forms with many EDITTABLES that are 5 or 6 columns and 4 to 6 rows, it is extremely frustrating for them to have to ENTER,ENTER, ENTER all the way through the EDITTABLE.
Of course, they could grab the mouse and click in the next control, but I do want to set up each form so that clients can use either the mouse OR keyboard to navigate the form. Is there a 'graceful' way to leave an edit table, one keystrock would be great, but two would be okay ? How could I setup (say) ALT J ('J' for jump) or some other standard key or even function key to leave the edit table ?
Somehow the key/s that are setup simply do a gotfocus on the next (tab order) control, I guess ?
Peter
At 17 OCT 1997 09:41AM Peter, Swiftscan systems Ltd wrote:
If you use CTRL+ENTER you will move to the next control in your tab order.
At 17 OCT 1997 10:50AM Cameron Revelation wrote:
Peter,
Ctrl-Tab to tab out of the edit table and Ctrl-Shift-Tab to go to the previous control.
Cameron. Revelation
—————————–56951330219958–
At 17 OCT 1997 11:39AM Don Bakke wrote:
Peter,
In addition to the fine responses from Peter and Cameron, you can setup your own method for exiting edittables, however you might not think it is 'graceful'
First, in the CREATE event of your window get your edittable to be qualified for the WM_SYSCHAR message:
rv=Send_Message(@Window:".ET_NAME", "QUALIFY_EVENT", "0x0106", 1) ; * WM_SYSCHAR
Then in the WINMSG for your edittable (using ET_NAME as my example) place the following code:
Hiword=Int(lParam/65536)
If Hiword EQ 8228 then ; * 8228 is the scan code for Alt-J
Cur_focus=Get_Property(@Window, "FOCUS")
Next_focus=Get_Property(Cur_focus, "NEXT")
rv=Set_Property("SYSTEM", "FOCUS", Next_focus)
end
The limitations to the above are:
1. Only works with Alt-key combinations. You might tweak it a little and play with WM_CHAR as well to get other variations.
2. Only works when the control that is NEXT in line is able to receive focus (e.g. not a disabled or symbolic field), unless you added some more code to look for the next available control that can receive focus.
Enjoy,
At 18 OCT 1997 05:09AM Peter Richards wrote:
Peter, Cameron & Don,
Thanks for the tips on leaving an Edit table,
Regards,
Peter