how to make a mouseup event called only once during a double click event?

[Techsatish]

how to make a mouseup event called only once during a double click
event?
here double click is made on a tree node in a tree control.

I have the code inside mouseup event....in runtime the mouseup is
called twice for the mouse double click over the selected tree node.

I want mouseup event to be called onece

Any ideas?

TIA
Satish

 

[Ken Halter]

how to make a mouseup event called only once during a double click
event?
here double click is made on a tree node in a tree control.

I have the code inside mouseup event....in runtime the mouseup is
called twice for the mouse double click over the selected tree node.

I want mouseup event to be called onece

Any ideas?

TIA
Satish

I'm just a visitor around here, but you seem to be trying to fight a design
that's been in place for around two decades. Mouse Up fires every time you
release the mouse button.

I dropped a textbox on a form in VB6, added a few debug.prints and got the
following output when I double-clicked.... (fwiw, the numbers are just the
VB timer value at the time)

'Form1:Text1_MouseDown 37502.56
'Form1:Text1_MouseUp 37502.64
'Form1:Text1_Click 37502.64
'Form1:Text1_DblClick 37502.71
'Form1:Text1_MouseUp 37502.81

So, if you're processing in MouseUp, seems like setting a boolean variable
called "ProcessMouseUp" or something similar = True in MouseDown and testing
that variable in MouseUp would be easy enough. Once the code in MouseUp
runs, reset that bool to False. Since MouseDown fires only once, the next
time MouseUp fires, your test should determine whether or not to take
action.

 

[gene kelley]

how to make a mouseup event called only once during a double click
event?
here double click is made on a tree node in a tree control.

I have the code inside mouseup event....in runtime the mouseup is
called twice for the mouse double click over the selected tree node.

I want mouseup event to be called onece

Any ideas?

TIA
Satish

If you are using the VB2005 TreeView control, you should look at using the NodeMouseClick and/or the
NodeMouseDoubleClick events rather than the standard Mouse Events.


Gene

 

[Techsatish]

Thanks Ken It works!
-Satish

I'm just a visitor around here, but you seem to be trying to fight a design
that's been in place for around two decades. Mouse Up fires every time you
release the mouse button.

I dropped a textbox on a form in VB6, added a few debug.prints and got the
following output when I double-clicked.... (fwiw, the numbers are just the
VB timer value at the time)

'Form1:Text1_MouseDown 37502.56
'Form1:Text1_MouseUp 37502.64
'Form1:Text1_Click 37502.64
'Form1:Text1_DblClick 37502.71
'Form1:Text1_MouseUp 37502.81

So, if you're processing in MouseUp, seems like setting a boolean variable
called "ProcessMouseUp" or something similar = True in MouseDown and testing
that variable in MouseUp would be easy enough. Once the code in MouseUp
runs, reset that bool to False. Since MouseDown fires only once, the next
time MouseUp fires, your test should determine whether or not to take
action.