[Oberon] Re: MT versus MTX.

peter at easthope.ca peter at easthope.ca
Wed Mar 26 17:29:28 CET 2014

From: peter at easthope.ca (Peter Easthope)
Date: Wed, 5 Mar 2014 09:03:08 -0800
> ... distinction between "mouse type" and "mouse type explicit".

From: jan at verhoeven272.nl (Jan Verhoeven)
Date: Thu, 6 Mar 2014 01:43:23 +0100
> Still, DetectMouse is in a funny place: it is after the mousetype was 
> set as 'value':
>                 SetMouseType(value);
>                 DetectMouse()

The order is logical.  First initialize a default value.  
Then try to detect.  
If detection fails, the default value remains.  
If detection succeeds, the detected value remains.

In familiar usage, NO is installed using Oberon-0.  Originally 
Oberon-0 ran from a diskette and you report running it under qemu.

In Oberon-0, the user typically sets the mouse type using 
the interactive graphical ConfigInput.SelectMouse.  Then 
config = "MTX" and DetectMouse is not invoked in Input.Configure. 
That is the familiar scenario.  

Still, the system allows for other scenarios.  One is where 
Oberon-0 is used to install the system and ConfigInput.SelectMouse
is omitted.  Then the mouse type is from DetectMouse.  I suspect 
that for a PS/2 mouse this is absolutely reliable.  For some mouse 
types, the type from DetectMouse might be less correct than the 
type from SelectMouse.

Thanks for your replies.

Sorry for cluttering the mailing list with these details.  For me 
they are crucial.

Regards,                   ... Peter E.

123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +1 360 639 0202  http://carnot.yi.org/  New address Bcc: peter at easthope. ca

More information about the Oberon mailing list