Windows 2000 Pushing Buttons

  • Thread starter Thread starter Sid Elbow
  • Start date Start date
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.
 
"Sid Elbow" <here@there.com> wrote in message
news:47a22a30$0$16227$c3e8da3@news.astraweb.com...
> 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.

Might be something as simple as a mouse with a bad
button contact. Use a different mouse for a few weeks -
they're cheap! It might also be that you move the mouse
slightly just before you press the button. Depending on
where you are, this won't work.
 
Pegasus (MVP) wrote:

> Might be something as simple as a mouse with a bad
> button contact. Use a different mouse for a few weeks -
> they're cheap!

No, it's happened on a couple of mice on this machine and on several
machines.


>It might also be that you move the mouse
> slightly just before you press the button. Depending on
> where you are, this won't work.

I think this is the most likely cause - my mouse technique. I think I
move the mouse slightly as I click. In Win3X (and perhaps Win9x) there
was a config entry that would make it more tolerant of this. I wondered
if something similar existed in the registry for Win2K but I've never
been able to track anything down doing internet searches.

(Plus, I still feel that if Windows responds by showing the button
depressing it's giving me feedback that it saw the button-push).
 
On Thu, 31 Jan 2008 17:51:50 -0500, Sid Elbow <here@there.com>
wrote:

>>Pegasus (MVP) wrote:
>>
>>> Might be something as simple as a mouse with a bad
>>> button contact. Use a different mouse for a few weeks -
>>> they're cheap!
>>
>>No, it's happened on a couple of mice on this machine and on several
>>machines.
>>
>>
>>>It might also be that you move the mouse
>>> slightly just before you press the button. Depending on
>>> where you are, this won't work.
>>
>>I think this is the most likely cause - my mouse technique. I think I
>>move the mouse slightly as I click. In Win3X (and perhaps Win9x) there
>>was a config entry that would make it more tolerant of this. I wondered
>>if something similar existed in the registry for Win2K but I've never
>>been able to track anything down doing internet searches.
>>
>>(Plus, I still feel that if Windows responds by showing the button
>>depressing it's giving me feedback that it saw the button-push).


Not completely sure about Win2K, but I think there was a window to
adjust the mouse in Tweakui v1.33 from Microsoft. Be sure and get
the 1.33 version, 'cause the 2.10.0.0 version is strictly for WinXP.
You can download a copy here:
http://www.annoyances.org/exec/show/tweakui

and from the annoyances.org web site:
<quote>
Windows Me, Windows 2000, Windows 98, and Windows 95

1. Download TweakUI (version 1.33).

2. Unzip tweakui.zip using an unzip utility, such as WinZip, and
place the files in a new folder in a convenient location, such as
your desktop.

3. Right-click on the tweakui.inf file and select Install to
install it on your system.

4. To start TweakUI, double-click the TweakUI icon in Control
Panel.

Note: there's a bug in this installer (it's been there since the
very first release, except for the new version for Windows XP). If
it prompts you to insert a disk or specify the location of the
Tweakui files, just point to the folder containing the files you
just unzipped, and click Ok.
<\quote>

HTH


--

The Seabat
GoogleGroups filtered with extreme prejudice.
 
If you "click and drag", but don't move far enough for the button to
relocate to a new destination, you will see the "button" depress and
nothing happens on release, except the "button" returns to the original
location. In other words, "by design".

Sid Elbow wrote:

> Pegasus (MVP) wrote:
>
>> Might be something as simple as a mouse with a bad
>> button contact. Use a different mouse for a few weeks -
>> they're cheap!
>
>
> No, it's happened on a couple of mice on this machine and on several
> machines.
>
>
>> It might also be that you move the mouse
>> slightly just before you press the button. Depending on
>> where you are, this won't work.
>
>
> I think this is the most likely cause - my mouse technique. I think I
> move the mouse slightly as I click. In Win3X (and perhaps Win9x) there
> was a config entry that would make it more tolerant of this. I wondered
> if something similar existed in the registry for Win2K but I've never
> been able to track anything down doing internet searches.
>
> (Plus, I still feel that if Windows responds by showing the button
> depressing it's giving me feedback that it saw the button-push).
 
The Seabat wrote:

> Not completely sure about Win2K, but I think there was a window to
> adjust the mouse in Tweakui v1.33 from Microsoft. Be sure and get
> the 1.33 version,

I have tweakui and had already looked in there. Doesn't seem anything
that would be related to this particular problem. There is a
double-click speed sensitivity setting but button-push involves only a
single click (I just used my previous win3 experience as an example of
the "hidden" settings in config files),
 
Bob I wrote:
> If you "click and drag", but don't move far enough for the button to
> relocate to a new destination, you will see the "button" depress and
> nothing happens on release, except the "button" returns to the original
> location. In other words, "by design".

Yes, that seems logical. But in that case, it would also be logical to
have a sensitivity setting buried somewhere. Particularly as I'm not
deliberately dragging and, if I'm accidentally doing so, it's by a tiny
amount.
 
Perhaps, but just a guess.

HKEY_CURRENT_USER\Control Panel\Desktop\DragHeight
and
HKEY_CURRENT_USER\Control Panel\Desktop\DragWidth



Sid Elbow wrote:

> Bob I wrote:
>
>> If you "click and drag", but don't move far enough for the button to
>> relocate to a new destination, you will see the "button" depress and
>> nothing happens on release, except the "button" returns to the
>> original location. In other words, "by design".
>
>
> Yes, that seems logical. But in that case, it would also be logical to
> have a sensitivity setting buried somewhere. Particularly as I'm not
> deliberately dragging and, if I'm accidentally doing so, it's by a tiny
> amount.
 
Bob I wrote:
> Perhaps, but just a guess.
>
> HKEY_CURRENT_USER\Control Panel\Desktop\DragHeight
> and
> HKEY_CURRENT_USER\Control Panel\Desktop\DragWidth

Thanks, Bob .... I'll play with them.
 
Hi,

Any chance you're sliding the arrow off the button before releasing it?
Pushing buttons down doesn't activate the commands, releasing the mouse
does.


---==X={}=X==---

Jim Self

AVIATION ANIMATION, the internet's largest depository.
http://avanimation.avsupport.com

Your only internet source for spiral staircase plans.
http://jself.com/stair/Stair.htm

Experimental Aircraft Association #140897
EAA Technical Counselor #4562
 
PA20Pilot wrote:
> Hi,
>
> Any chance you're sliding the arrow off the button before releasing it?
> Pushing buttons down doesn't activate the commands, releasing the mouse
> does.
>
>
> ---==X={}=X==---
>
> Jim Self

Well, I'm certainly not completely sliding off but it's quite likely
that I am moving the mouse a little before releasing in which case
BobI's suggestion may help. I've actually doubled the DragHeight and
DragWidth values and I'll run with it for a while and see if it improves.
 
Back
Top