🚀 go-pugleaf

In article <bjorn.759011529@hal.ludd.luth.se> bjorn@ludd.luth.se (Bjorn Fahller) writes:
>In <2hjeu1$ben@linus.mitre.org> dbrake@cyclone.mitre.org (Dennis Brake (PSI) X7767) writes:
>
>>In article <2hi09s$1302@thebes.cc.waikato.ac.nz> hamish@waikato.ac.nz writes:
>>...
>>>Simple. Make button 1 pick up the icon like god intended it... This button
>>>2 bit is a real pain...
>>Agreed.
>
>This, I don't understand. On most mice, button 2 is fairly close to button one,
>so it really doesn't make it much more of an effort :)
>
>I can give one good argument against moving stuff around with MB1, though.
>On every system I've yet used, and every program too, that either only used
>one mouse button, or used the same mouse button for moving stuff as for
>highlighting and opening, I manage to move things by accident.
>
>Out of curiosity; what would a good way to select several icons be if MB1 was
>used for moving?
>   _

My favorite mouse setup is:
     MB1 - SELECT
           used for selects (using a click) drag (pushing and holding)
     MB2 - EXTEND
           select additional items/icons (using a click) 
           selecting more text in the editor (using click or drag)
     MB3 - MENU
           popup a menu for the item. If this button is clicked the
           menu is posted and remains up until a selection is made
           (this is the OS/2 behavior). If this button is held down
           the menu is popped up and you drag to the selection. If
           you release the button without making a selection the menu
           is popped down. If we had this second behavior, we could go
           to the desktop, push  and hold MB3, see the processes, release
           MB3 and the list would popdown.

Dennis