S
Sid Elbow
Something that's bothered me for years and I wondered if anyone could
shed some light:
Not infrequently when I use the mouse to push a screen "button", I'm
perhaps a bit sloppy, the button-push isn't seen and I have to do it
again more carefully ...
..... and yet, sloppy or not, I actually *see* the button depress. Thus
Windows sure as heck knows I pushed it so why doesn't it respond? It's
almost like pushing a button on the TV remote and not pressing hard
enough. Surely Windows buttons aren't pressure-sensitive.
This kind of reminds me of a problem I used to have in Win3X days where
a double-click wouldn't take. After messing with the double-click speed
to no avail I finally learned that there was a config file entry related
to the amount of movement of the mouse between clicks - and that fixed
the problem completely. I wondered if there was perhaps a registry entry
related to what I'm seeing here.
shed some light:
Not infrequently when I use the mouse to push a screen "button", I'm
perhaps a bit sloppy, the button-push isn't seen and I have to do it
again more carefully ...
..... and yet, sloppy or not, I actually *see* the button depress. Thus
Windows sure as heck knows I pushed it so why doesn't it respond? It's
almost like pushing a button on the TV remote and not pressing hard
enough. Surely Windows buttons aren't pressure-sensitive.
This kind of reminds me of a problem I used to have in Win3X days where
a double-click wouldn't take. After messing with the double-click speed
to no avail I finally learned that there was a config file entry related
to the amount of movement of the mouse between clicks - and that fixed
the problem completely. I wondered if there was perhaps a registry entry
related to what I'm seeing here.