Repeat Question

[Stephen Saunders]

Hello,

I am new to this news group. Please forgive me if this has been asked
before.

In my VB application, I have next and previous command buttons. I would
like to be able to hold the left mouse button down on these buttons and have
the operation repeat. Is this a property?

adTHANKSvance,

Stephen Saunders

[J French]

On Fri, 04 Mar 2005 10:50:04 GMT, "Stephen Saunders"
<kd****@earthli nk.net> wrote:

Hello,

I am new to this news group. Please forgive me if this has been asked
before.

In my VB application, I have next and previous command buttons. I would
like to be able to hold the left mouse button down on these buttons and have
the operation repeat. Is this a property?

A Timer ?

[J French]

On Fri, 04 Mar 2005 10:50:04 GMT, "Stephen Saunders"
<kd****@earthli nk.net> wrote:

Hello,

I am new to this news group. Please forgive me if this has been asked
before.

In my VB application, I have next and previous command buttons. I would
like to be able to hold the left mouse button down on these buttons and have
the operation repeat. Is this a property?

A Timer ?

[J French]

On Fri, 04 Mar 2005 10:50:04 GMT, "Stephen Saunders"
<kd****@earthli nk.net> wrote:

Hello,

I am new to this news group. Please forgive me if this has been asked
before.

In my VB application, I have next and previous command buttons. I would
like to be able to hold the left mouse button down on these buttons and have
the operation repeat. Is this a property?

Oops - also you'll need to use the MouseDown and MouseUp events, and
get rid of the Click

I would wrap it in a UserControl (NOT OCXed) and call it something
like a PulseButton

[J French]

On Fri, 04 Mar 2005 10:50:04 GMT, "Stephen Saunders"
<kd****@earthli nk.net> wrote:

Hello,

I am new to this news group. Please forgive me if this has been asked
before.

In my VB application, I have next and previous command buttons. I would
like to be able to hold the left mouse button down on these buttons and have
the operation repeat. Is this a property?

Oops - also you'll need to use the MouseDown and MouseUp events, and
get rid of the Click

I would wrap it in a UserControl (NOT OCXed) and call it something
like a PulseButton

[Shell]

In responce to the post:
On Fri, 04 Mar 2005 10:50:04 GMT, "Stephen Saunders"
<kd****@earthli nk.net> stated...and I replied:

Hello,

I am new to this news group. Please forgive me if this has been asked
before.

In my VB application, I have next and previous command buttons. I would
like to be able to hold the left mouse button down on these buttons and have
the operation repeat. Is this a property?

adTHANKSvanc e,

Stephen Saunders

You may do better changing the 2 command buttons into a single
horizontal scrollbar control. If you size it down so only the 2 (left
& right) buttons show, it will look like 2 command buttons with left
and right arrows.

Just a thought,
Shell
-
http://drshell.home.mindspring.com/
Into computers since 1972.
WARNING! Information and e-mail addresses contained herein, are for personal use only. By entering this site, you agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to: allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone. Violators will be dealt with accordingly.
-

[Shell]

In responce to the post:
On Fri, 04 Mar 2005 10:50:04 GMT, "Stephen Saunders"
<kd****@earthli nk.net> stated...and I replied:

Hello,

I am new to this news group. Please forgive me if this has been asked
before.

In my VB application, I have next and previous command buttons. I would
like to be able to hold the left mouse button down on these buttons and have
the operation repeat. Is this a property?

adTHANKSvanc e,

Stephen Saunders

You may do better changing the 2 command buttons into a single
horizontal scrollbar control. If you size it down so only the 2 (left
& right) buttons show, it will look like 2 command buttons with left
and right arrows.

Just a thought,
Shell
-
http://drshell.home.mindspring.com/
Into computers since 1972.
WARNING! Information and e-mail addresses contained herein, are for personal use only. By entering this site, you agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to: allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone. Violators will be dealt with accordingly.
-

[five of nothing]

What J French is saying is to do something like the following:
Add a timer for each button, say TmrNext and TmrPrev. Set their
interval property to the repeat time (how often does it repeat the
click), in milliseconds.
Then, instead of a CmdNext_Click event that looks like this:
Sub CmdNext_Click()
[do stuff]
End Sub

Make a CmdNext_MouseDo wn event that looks like this:
Sub CmdNext_MouseDo wn()
TmrNext_Timer()
TmrNext.Enabled = True
End Sub

And put the [do stuff] in the TmrNext_Timer() event:
Sub TmrNext_Timer()
[do stuff]
End Sub

Finally, add a CmdNext_MouseUp () event to disable the timer:
Sub CmdNext_MouseUp ()
TmrNext.Enabled = False
End Sub

That way, when the user presses the button, it will set off the
MouseDown event. This will first run the TmrNext_Timer() event, which
just does the [do stuff]. Then it will set the timer ticking. Then
every time the timer goes off, it'll do the [do stuff] again. When
they let go of the button, CmdNext_MouseUp (), the timer will be
stopped, so [do stuff] won't happen again.

You would, of course, do the same for CmdPrev. And because all this is
a lot to do twice and would be useful, wrapping it in a UserControl
would be helpful, but not necessary.

The only problem with this plan that I see is that if they clicked and
then dragged off the button to let go (Triggering MouseDown but not
MouseUp), the [do stuff] would keep happening until they clicked the
button again (Triggering MouseDown _and_ MouseUp). But this problem is
easily worked around (click the button again).

[five of nothing]

What J French is saying is to do something like the following:
Add a timer for each button, say TmrNext and TmrPrev. Set their
interval property to the repeat time (how often does it repeat the
click), in milliseconds.
Then, instead of a CmdNext_Click event that looks like this:
Sub CmdNext_Click()
[do stuff]
End Sub

Make a CmdNext_MouseDo wn event that looks like this:
Sub CmdNext_MouseDo wn()
TmrNext_Timer()
TmrNext.Enabled = True
End Sub

And put the [do stuff] in the TmrNext_Timer() event:
Sub TmrNext_Timer()
[do stuff]
End Sub

Finally, add a CmdNext_MouseUp () event to disable the timer:
Sub CmdNext_MouseUp ()
TmrNext.Enabled = False
End Sub

That way, when the user presses the button, it will set off the
MouseDown event. This will first run the TmrNext_Timer() event, which
just does the [do stuff]. Then it will set the timer ticking. Then
every time the timer goes off, it'll do the [do stuff] again. When
they let go of the button, CmdNext_MouseUp (), the timer will be
stopped, so [do stuff] won't happen again.

You would, of course, do the same for CmdPrev. And because all this is
a lot to do twice and would be useful, wrapping it in a UserControl
would be helpful, but not necessary.

The only problem with this plan that I see is that if they clicked and
then dragged off the button to let go (Triggering MouseDown but not
MouseUp), the [do stuff] would keep happening until they clicked the
button again (Triggering MouseDown _and_ MouseUp). But this problem is
easily worked around (click the button again).

[Steve Gerrard]

"five of nothing" <50**@mailinato r.com> wrote in message
news:11******** **************@ l41g2000cwc.goo glegroups.com.. .

The only problem with this plan that I see is that if they clicked and
then dragged off the button to let go (Triggering MouseDown but not
MouseUp), the [do stuff] would keep happening until they clicked the
button again (Triggering MouseDown _and_ MouseUp). But this problem is
easily worked around (click the button again).

Actually that is not a problem. Even if they drag away from the command button,
it will still receive the MouseUp event when the user releases the button. The X
and Y values will just be outside the boundaries of the command button.