New
#31
Where I work, I actually see people triple-clicking, hahaha
One other reason for me keeping with the double click is that it is a more considered procedure.
With a lot of systems I have worked with over the years an accidental click could have disastrous consequences.
Although the dangerous actions will of course have confirmation dialogues and other safeguards, for the operators, these would sometimes need to be disabled during the live maintenance and testing phases.
The old engineering adage "measure twice, cut once" is still valid in the digital age :)
Always single click.
That and mouse speed are a few of the first things I do after an install.
i double-click inside windows explorer out of long habit - it means i can change my mind when half-way through. it makes perfect sense to me that single-click means 'select', and double-click means 'do something'.
i've got used to single-clicking on shortcuts within startmenu and taskbar, but like to keep double-click when dealing with files.
i've got a highly sensitive gaming mouse, and have to turn it down when working on the desktop.
If i would change mine to single click now i would open something i click on multiple times. Im so used to double click now.
The lasagna ain't ready and I can use another glass o' red...
That means:... can change my mind when half-way through.
LButtonDown, then, LButtonUP, for the Single click. (Unless selected otherwise by the Lefty)
FWIW,
Dunno about MS Windows,
but having programmed for unix X_stuff, I think one must "request" an operator's mouse_actions,
i.e. (L/R)ButtonDown, (L/R)ButtonUp, MouseRoll_Coordinates (Scaled IAW Screen_Coord_Mapping), etc.
Don't remember anything about Single_Click, Dbl_Click, etc,
but I think that your s/w must have tracked the Dn_button, if and when it sees an Up_button,
to determine that a "Single-click" was fully accomplished.
Your s/w has to do 'whatever', depending upon:
What your sw has requested (sort-of: 'registered-for'), and then your program "Does-it",
when it gets control from the (Driver/OS/src) because of Bruno the operator's actions, etc.
I think they call this stuff "Callback", or something. Roughly...
So, if one chooses, the sytem can be shut-down (or whatever), on the first mouse L_Button_Down. (Or 23rd/95th, if you keep a counter)
Can't imagine MS Windows APIs being too much more "innovative"...
Certainly, Developers and Programmers can comment here.