[Coco] Um3.init help needed

[gene heskett]

On Saturday, December 10, 2011 01:32:07 PM Bill Pierce did opine:

> I have looked through the tons of source code from Ultimuse3 and it
> seems (and I should have known) that the only real choices in
> programming in standard OS9 for a mouse is through the built in system
> calls. The choices here are regular joystick reads, Hi-res joystick
> interface (Bjork's I think) and the keyboard mouse (<shift clear> I
> think?) for using <shift-arrow> keys for a mouse then I think it it was
> F1 & F2 for fire buttons. I found some old source code for a serial
> mouse and was glancing through it and if yours is similar, then it uses
> a "driver" instead of going through the standard system calls. So the
> serial mouse would for the most part not be traveling the same paths as
> a standard mouse and unless the software specifically allows the use of
> the driver then the mouse will be missed (I may be wrong here, comment
> welcome). If there is support for the serial mouse within OS9's def
> files and C libs then Umuse3 would have to be recompiled from source
> with a third choice to use it. The only choices I saw in the source was
> standard and hi-res. The key-mouse in built into OS9 itself, so for now
> that would most likely be your best bet (to use the key-mouse). I
> remember when I first got Umuse3, I didn't own a mouse and I had junked
> my joystick to make an audio-in cable for sampling through the 6-bit
> DAC and I had to use the key-mouse feature and got along ok till I
> found one of the old "black" mouse's (mice?) on the manager's special
> table at "The Shack". I will contact Mr. Knudson and see if he has any
> suggestions as well
> 
> Bill Pierce
> ooogalapasooo at aol.com

Thanks Bill.  As far as the mouse is concerned, I should do some 
experimenting with the SS.Mouse call I suppose to see if that works. I 
tried to follow the l51defs as much as practical but had to correct what 
looked like an off by one mistake at one point.  But all the mouse data is 
present and accounted for in that 8 byte packet specified in l51defs.  In 
fact, truth be known, it could probably be condensed into 5 bytes, with the 
first one being button status (all 3 buttons) and the next 2 ints being the 
H & V position.  At the time I originally set it up, there was a patch for 
cc3io, and this mouse then worked with multivue, and with icnedit, which 
used all 3 buttons.  But with things being separated out into subroutines 
over the last decade, I do not know if the present hires mouse works the 
same in terms of dumping its data into this 8 byte packet.  If I can find a 
hires adaptor in my junk box, I may build a boot disk and verify that data 
packet again.  If they match, then any sw using the SS.Mouse call family 
should Just Work(TM). Sw that used its own mouse stuff is likely going to 
be DOA though.

But as it turns out, what docs I have says that ubox3 doesn't use the mouse 
at all.  :(
[...]
Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene>
This sentence does in fact not have the property it claims not to have.