Disable Double-Click?

>I have an app (A2000) where I am letting the user move an object on the
>screen. I use the OnClick for a command button event to modify the
>object's Top (or Left) properties, but you can only click slowly. That is,
>every other click is ignored, because Access is seeing a double click
>event. I would put the same code there, except I'm also using the SHIFT
>key (during mouse click) to cause bigger moves, and there's no SHIFT flag
>for the OnDoubleClick event.
>
Can anyone see a way around this? Something with OnKeyPress? Haven't
played around there yet. If I could get to the double-click timing on the
PC's mouse properties... hmmm, I don't think I'd want to mess with that.
I've tried to simulate drag-n-drop, but it's pretty cheesy. And I like to
be able to control the exact move increments, to help with object
alignment (sort of snap-to-invisible-grid).
>

My recollection was that if you had both Click and DoubleClick events, the
(Single) Click event would fire prior to the Double Click. I just tried
that to refresh my memory and that is exactly what happened; then I simply
removed the code from the DoubleClick event, and double clicked -- only
the Click event fired.
>
"Way around _what_", specifically? Sounds to me you may want to use
control panel and settings to change the interval between clicks for
double click. Or put in an empty DoubleClick event.
>
Larry Linson
Microsoft Access MVP
>
>
>
"Armando" <armando@bogus.comwrote in message
news:cE9yg.27$Db4.1186@news1.epix.net...>
>

>I have an app (A2000) where I am letting the user move an object on the
>screen. I use the OnClick for a command button event to modify the object's
>Top (or Left) properties, but you can only click slowly. That is, every
>other click is ignored, because Access is seeing a double click event. I
>would put the same code there, except I'm also using the SHIFT key (during
>mouse click) to cause bigger moves, and there's no SHIFT flag for the
>OnDoubleClick event.
>
>Can anyone see a way around this? Something with OnKeyPress? Haven't
>played around there yet. If I could get to the double-click timing on the
>PC's mouse properties... hmmm, I don't think I'd want to mess with that.
>I've tried to simulate drag-n-drop, but it's pretty cheesy. And I like to
>be able to control the exact move increments, to help with object alignment
>(sort of snap-to-invisible-grid).
>

I have an app (A2000) where I am letting the user move an object on the
screen. I use the OnClick for a command button event to modify the object's

Armando wrote:>
To do this I use the MouseDown Event as follows:
>
Private Sub lblSpeedControl_MouseDown(Button As Integer, Shift As
Integer, X As Single, Y As Single)
Dim NewTop As Single
Dim pY As Single
Dim pX As Single
Dim c As Single
Dim p As POINTAPI
Dim r As Single
Dim t As Long
t = lblSpeedControl.Top
If Button = acLeftButton Then
GetCursorPos p
pX = p.X
pY = p.Y
With lblSpeedControl
Do While Not CBool(GetQueueStatus(QS_MOUSEBUTTON))
GetCursorPos p
SetCursorPos pX, p.Y
NewTop = t + (p.Y - pY) / mPixelsPerTwipVerticalFactor
If NewTop < mMinTop Then
If .Top <mMinTop Then
.Top = mMinTop
SpeedControlColor
Me.Repaint
If mMinTop - NewTop 28 Then Exit Do
End If
ElseIf NewTop mMaxBottom Then
If .Top <mMaxBottom Then
.Top = mMaxBottom
SpeedControlColor
Me.Repaint
If NewTop - mMaxBottom 28 Then Exit Do
End If
Else
.Top = NewTop
SpeedControlColor
Me.Repaint
End If
Loop
End With
SetCrementInterval lblSpeedControl.Top / mMaxBottom
End If
End Sub
>
Of course this calls other functions, but perhaps you can get the idea.
The Double Click never comes into play here, as
GetQueueStatus(QS_MOUSEBUTTON) monitors any change (such as releasing
the left button) and stops dragging the control.
>

>Hi Tom -
>
>For your indulgence: I'm using EIGHT buttons to move and size rectangles
>which represent the arrangement of real-world items, which are managed one
>at a time by clicking on them (in non-design mode).
>
>To your suggestion - AutoRepeat sounds pretty good. I just tried it, and
>the new location doesn't display until the mouse is released. But it DOES
>keep moving while pressed, you just have to let go to see how far. This
>might be acceptable, it's one of the better ideas so far.
>
>Thanks for your interest,
>
>Armando
>