#: 17783 S12/OS9/68000 (OSK)
    23-Mar-93  13:32:55
Sb: #17767-#Subroutine modules
Fm: Graham Trott 100115,1075
To: Bob van der Poel 76510,2203 (X)

Bob --

>>> At this point, however, it looks like it'll be easier for all (including
the folks who will end up writing there own interfaces) to have this done via a
front-end which interprets mouse data, etc. and inserts it into the keyboard
stream for ved. <<<

Another possibility is to have the mouse interface written as a separate
stand-alone process with a defined data module interface.  All the editor needs
to know is the name of the mouse module (could be in an environment variable)
so it can fork it.  Advantages of this approach are 1) there are no
side-effects mixing mouse info with keyboard input and 2) the data module can
contain fields that time-stamp mouse events, allowing double-click or
inactivity detection, mouse acceleration and so on.  The editor is relieved of
the need to handle all this real-time junk.  Timing gets a bit imprecise when
everything has to feed through stdin.

-- GT

There is 1 Reply.