A USB adapter for a classic Depraz mouse
jfloren.net
jfloren.net
To this day I buy gaming mice because you can easily add weights to them at your discretion.
Didn't know what a human hand looks like?
i loved the mice that came with sparc workstations. remember those first optical mice that needed a special metallic mousepad with a grid on them?
they were wide and flat. held with my thumb and little finger only. no other touch. that's how i use a mouse. but todays mice are all to small, so that i have to squeeze my fingers into an unnatural position.
i wish someone would design a flat and wide mouse like that again.
if i had small hands, more mice might fit.
for a comfortable hold using only fingertips, a mouse would have to be 8-9cm wide.
But than again fishermen would use their teeth to clamp weights on the fishing line.
Delightful mouse-related trivia aside, making wine caps out of lead up till 1980s is quite a civilisational own-goal — can’t even avoid touching it.
Even Romans knew lead was toxic. Maybe the lead-induced violence hypothesis is correct after all.
I will say that it was remarkably accurate. Somehow I remember it being very good at its positioning. But the 5620 was mainly being used for text so pointing accuracy may have been moot.
I remember it doing sort of x/y axis lines like the graticule in a gunsight to mark its point.
I also remember 4 buttons of different colours.
Good point, seems like X1 will be low after the x interrupt occurs. So they could read just x2 only. But my guess is that they were testing the xint() and yint() functions using polling, then configured the interrupts later.
If the switch bounces you can get spurious interrupts. If the maximum bounce period is under the time it takes the Arduino to process the interrupt and call your handler so that you can be sure the pin will be done bouncing by the time your code runs than you can handle this by simply treating the interrupt as an opportunity to poll.
If the switch bounce can be longer than that then you might need software debouncing. Probably the simplest approach there is keep track of the last interrupt time and only treat interrupts as real if they do not occur too soon after the previous interrupt.
In my experience, the majority of old mice were not very good, so it's not surprising that most adapters go in the opposite direction (new mouse into old computer).
The person who develops these has some cool blog posts on the development process