🚀 go-pugleaf

I've been suffering a sore hand. I'm looking for a better mouse but there is
_another_ approach.

Would anyone care to write a module to intercept and translate the standard
mouse events?

It has been criticised than Acorn's standard of a double mouse click is far from
intuitive. It is also far from friendly to the user's hand. We're (probably)
stuck with it but there may be a sensible way round it...

When do we _really_ need a double select click? What do we actually do with a
double select click that we could not do some other way? Seems to me that I
actually use the double click far more than the single one. If I really need to
do the single click operation there is almost always another way to do it
(usually use the adjust button or even the menu button).

What is needed is a mouse event translation module. Initially I would simply
intercept the singe mouse select click and output it as a double select click.
This should be pretty simple.

If the module programmer wants to get fancy then how about a user configurable
translation module: it could intercept mouse events and certain keys and output
other events.

Any programmers out there interested in taking the idea futher?
-- 
-------------------------------------------------------------------------
Richard Torrens  - 4qd@argonet.co.uk

---------- We use an Acorn RISC-PC 32 bit RISC computer  ----------------