[<<Previous Entry]
[^^Up^^]
[Next Entry>>]
[Menu]
[About The Guide]
Mouse Support:
----------------------------------------------------------------------------
Mouse support is almost automatic with this release of TSDWIN. If
you intend to use TSDWIN interface functions exclusively, you need
make only one call to twMouseInit() to take advantage of the built
in mouse support. All (?) user interface functions, like
twButtonBox() and the new browses have automatic mouse support. In
most cases, the left hand button is used to select and the right
hand button to escape. Sometimes, in the new twACChoice()
function, the right hand button may be defined to allow tagging
multiple array elements. When on a vertical scroll bar, the right
hand button is used to page a browse display, the left hand button
move the highlight one line. We did not like the idea of dragging
the mouse to move the highlight bar. We have made the highlight
bar move with the mouse when it is in a browse area for menus and
popup boxes. In the full fledged browses, twRABrowse(),
twABBrowse(), and twBRBrowse(), you must click in a field or array
element region to move the highlight. If editing is allowed, a
double click can be made to allow editing, or if not allowed,
selecting.
NOTE: All TSDWIN functions with built-in mouse support assume the
mouse is OFF on entry. This allows the library functions to
retain control of the mouse cursor. If you call functions
with ActionKeys or Mouse Hot Spots, you may have to
temporarily take charge of the mouse cursor display.
We have made every attempt to make it possible for programmers
with little mouse experience to provide a professional and
accurate mouse interface with only one function call.
For those who wish to design their own mouse routines, the ASM
calls to Interrupt 33h are available, as well as some TSDWIN
mouse specific functions, which, for instance, change the BIOS
return to the familiar Clipper Row and Column scheme. Some of
these Clipper mouse functions are definitely 'BETA' in TSDWIN
version 1.50. There are functions for retaining hot spots with the
library call, but the browses in TSDWIN retain the hot spots in
the caller, a procedure we feel makes more sense than creating yet
another static stack. If you use the stack functions, you MUST
remember to free up memory when you are finished with it, or your
application can grind to a halt as VMM finds it has to swap more
often.
The detailed function descriptions give full explanations of how
each TSDWIN moused function works. As with everything in TSDWIN,
they are all tied to the 'window ' concept in order to give your
entire application a coherent look and feel.
This page created by ng2html v1.05, the Norton guide to HTML conversion utility.
Written by Dave Pearson