Kempston mouse: Bottom line!

Due to one sensible proposal in the driver, the wheel is hung on 6.7 bits
port #FADF.
D6 - up
D7 - down
I won’t redo anything, since these disputes will again drag on to
infinity.

In the near future, support for the wheel should appear in UnReal Speccy! (when
the author buys himself a mouse with a wheel ;)
Also there should be such a thing as translating the wheel to up/down cursors
(for more convenient page browsing).
It’s unlikely that it will be possible to write a plugin for Shalaev due to problems with the wheel under the DOS.

PS: By the way, maybe someone is interested. I will submit the mouse driver as a course project on System Software.

2Real: Will you soon throw RC 2.1 into the echo?

[I ZX] !mPeR!0

PD> In connection with one sensible proposal in the driver, the wheel is hung on
PD> 6.7 bits of the #FADF port. D6 - up D7 - down I won’t redo anything
PD>, since these disputes will again drag on ad infinitum.

Damn... I told you... You need to do something on the counter... Bits next. :

D0 - left
D1 - right
D2 - middle

D3 - 0 digit of the wheel counter
D4 - 1 -//-
D5 - 2 -//-
D6 - 3 -//-

----------------------------------------------------------
People, what do you think? This is more correct, more logical and more reliable in terms of circuit design.
The counter can be made not 4-bit, but 3, for example... This is no longer a fundamental question..

PD> In the near future, support for the wheel should appear in UnReal Speccy!
PD> (when the author buys himself a mouse with a wheel ;) Also there should be such
PD> something like translating the wheel to up/down cursors (for more convenient
PD> leafing through the press). It is unlikely that it will be possible to write a plugin for Shalaev due to
PD> problems with the wheel under the dos.

PD> PS: By the way, maybe someone is interested. I will submit the mouse driver as a
PD> course project in System Software.

17 Nov 01 12:45, Pavel Demchuk wrote to All:

PD> Due to one sensible suggestion in the driver, the wheel is hung on
PD> 6.7 bits of the #FADF port. D6 - up D7 - down I don't need to redo anything

Have you done this in real life?

PD> Wheel support should appear in UnReal Speccy in the near future!

That says it all...

PD> --- GoldED 3.00.Alpha5+

PD>> to 6.7 bits of the #FADF port. D6 - up D7 - down I won't redo anything
PD>>, since these disputes will again drag on until
PD>> infinity.

OM> Damn... I told you... On the counter you need to do... Bits next. :

OM> D0 - left
OM> D1 - right
OM> D2 - middle

OM> D3 - 0 digit of the wheel counter
OM> D4 - 1 -//-
OM> D5 - 2 -//-
OM> D6 - 3 -//-

OM> ----------------------------------------------------------------------
OM> -- People what do you think? This is more correct, more logical and more reliable in terms of
OM> circuit design. The counter can be made not 4-digit, but 3, for example...
OM> This is no longer a fundamental question..

But in my opinion, no counters are needed, who can scroll the wheel
more than 50 clicks (lines of text) per second? As I assume
the principle of operation of the wheel is as follows: when scrolling up or down,
we get not a constant 1, but a sequence of 100001000010000,
depending on the speed of rotation of the wheel. So if you need
some kind of counter, it should be a software one, and not in the mouse driver itself,
the driver should only output the status of port 0/1.

I wonder how you were going to read the counter value? Then
we would have to enter some kind of strob signal so that the mouse
controller would know that we have already counted the counter and it can be reset and
start counting fromнуля :).

* Crossposted in REAL.SPECCY
* Crossposted in ZX.SPECTRUM

Bye!
Pa...@nm.ru www.realsoft.hotbox.ru [RC 2.0] [Real Software]

Tuesday 20 Nov 2001 12:21:11, Pawel Kislyak -> Oleg Maxsimuk:

PK> And in my opinion, no counters are needed, who can scroll the
PK> wheel
PK> by more than 50 clicks (lines of text) per second? How do I

The wheel can be hung not only on the scroll by the way.

PK> I wonder how you were going to read the counter value?
PK> Then
PK> you would have to enter some kind of strob signal so that the
PK> controller
PK> of the mouse knew that we had already counted the counter and it can be reset and
PK> start counting from scratch :).

And how do you read XY coordinates? Look at the physical interface diagram (4
IE11, 2 AP5, 1 ID7, 1 LP8, 1 TL1). The counters count pulses constantly, without
any zeroing, and the processor reads them when it accesses the driver.
It is completely similar to adding a wheel: one IE11 will be added, one AP5,
LP8 will be removed.

Regards, Dmitriy.