🚀 go-pugleaf

In article <2hg27t$1f9@panix2.panix.com>, wookie@panix.com (Steve Houle) writes:

 > > When I press mouse button 2, nothing happens.  I have to move the mouse
 > > at least 5 pixels before the icon is picked up and start moving with the
 > > pointer.  This is very annoying, [...]
 > 
 > So if the icon is picked up immediately, then how do you expect OS/2 to
 > know when you REALLY wanted the object's menu to pop up?
 > 
Pop up the menu when the button is released without moving the icon.  Or when
the pointer isn't moved outside the icon, so that no movement would happen
anyway.

 > >2. It should be possible to move the mouse pointer by using the keyboard.
 > >Something like ctrl+shift+alt+arrow keys could be used.  Several
 > >shareware programs (and the install routine...) don't support the keyboard
 > >properly.
 > 
 > Third party mice (like the PCMouse I use) aren't supported by the install
 > program.  So I know for a fact that you can do anything with the keyboard
 > you can do with the mouse during an install.  Also, I took the time to
 > learn what many of the keystrokes are, and find the WPS is sometimes
 > faster via the keyboard.

Somewhere during install there is a check box for "migrating".  I don't
want to migrate anything, but I am unable to reach this box as the
"enter" button has focus. I know I usually can move the focus around
with the arrow keys and the TAB key, but I can't move focus to the
check box.  I get back to this dialog after backing out of the migration
box, and it is suddenly possible to move the focus around.  This isn't
possible before that.  A small bug perhaps, but it is there.

Why in the world isn't third party mice supported during install?
The correct (mouse systems) driver is selected before the second boot, so this
shouldn't be a problem at all.  
 > 
 > >3. Mouse button 3 is "undefined".   Give those of us that have it a
 > >possibility to configure it to do something useful/timesaving.
 > 
 > Those of you that have mice with 18 buttons should get your mouse driver
 > from the mouse vendor, NOT IBM.  I understand the shareware mouse driver
 > RODENT.SYS does some of what you want.

IBM is providing drivers for some 3-button mice, a listbox with possible events
for the third button isn't that complicated to add.  Please don't say that IBM
shouldn't provide drivers for non-IBM hardware.  There was a time when os/2
wasn't supposed to run on non-IBM machines.  If os/2 is going to be popular, then
it needs to support all popular hardware, and work well with it too.