button click event - simple question

[Bernie Yaeger]

If the user clicks the processit button, the click event code runs. What
happens if he/she clicks it again before it's done processing? Does the
system remember and process twice? Does it ignore a button click if the
waitcursor is active but not if the default cursor is active?

OK - I apologize - 2 questions.

Tx,

Bernie

[Armin Zingler]

"Bernie Yaeger" <be*****@cherwellinc.com> schrieb

If the user clicks the processit button, the click event code runs.
What happens if he/she clicks it again before it's done processing?
Does the system remember and process twice?
Yes, the click event is stored in the message queue and processed as soon as
the previous event(s) has been processed.

More info:
http://msdn.microsoft.com/library/en...sagequeues.asp
Does it ignore a button
click if the waitcursor is active but not if the default cursor is
active?

The behavior does not depend on the cursor, but you should set the cursor
depending on the application/window state.
--
Armin

http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html

[Herfried K. Wagner [MVP]]

* "Bernie Yaeger" <be*****@cherwellinc.com> scripsit:

If the user clicks the processit button, the click event code runs. What
happens if he/she clicks it again before it's done processing? Does the
system remember and process twice?
The button click will be queued.
Does it ignore a button click if the
waitcursor is active but not if the default cursor is active?

How do you activate this cursor?

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Bernie Yaeger]

Hi Herfried,

me.cursor = cursors.waitcursor

Is there a better way?

Bernie

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:bq*************@ID-208219.news.uni-berlin.de...

* "Bernie Yaeger" <be*****@cherwellinc.com> scripsit:

If the user clicks the processit button, the click event code runs. What happens if he/she clicks it again before it's done processing? Does the
system remember and process twice?

The button click will be queued.

Does it ignore a button click if the
waitcursor is active but not if the default cursor is active?

How do you activate this cursor?

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Herfried K. Wagner [MVP]]

* "Bernie Yaeger" <be*****@cherwellinc.com> scripsit:

me.cursor = cursors.waitcursor

Is there a better way?

This AFAIR won't block any events.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Bernie Yaeger]

Hi Herfried,

Is there a generic way to set up a waitcursor such that it will block
repress?

Tx for your help, as always,

Bernie
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:bq*************@ID-208219.news.uni-berlin.de...

* "Bernie Yaeger" <be*****@cherwellinc.com> scripsit:

me.cursor = cursors.waitcursor

Is there a better way?

This AFAIR won't block any events.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Chris Dunaway]

On Tue, 2 Dec 2003 15:26:47 -0500, Bernie Yaeger wrote:

happens if he/she clicks it again before it's done processing? Does the

If you wish to prevent this, disable the button in the click event and then
re-enable it when the click event is finished.

Or, set a boolean to indicate that the code is already in the processing of
the method:

If bAlreadyProcessing then
Exit Sub
Else
bAlreadyProcessing = True
Endif

'.... Processing code here

bAlreadyProcessing = False
Just some ideas
--
Chris

To send me an E-mail, remove the underscores and lunchmeat from my E-Mail
address.

[Armin Zingler]

"Chris Dunaway" <dunawayc@_lunchmeat_sbcglobal.net> schrieb

On Tue, 2 Dec 2003 15:26:47 -0500, Bernie Yaeger wrote:

happens if he/she clicks it again before it's done processing?
Does the
If you wish to prevent this, disable the button in the click event
and then re-enable it when the click event is finished.

This does not work because the button will be enabled again when the click
is received.
Or, set a boolean to indicate that the code is already in the
processing of the method:

If bAlreadyProcessing then
Exit Sub
Else
bAlreadyProcessing = True
Endif

'.... Processing code here

bAlreadyProcessing = False

Same as above. It only makes sense when you use Application.Doevents during
the process.
--
Armin

http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html

[Armin Zingler]

"Bernie Yaeger" <be*****@cherwellinc.com> schrieb

Is there a generic way to set up a waitcursor such that it will
block repress?

As I've already written, the look of the cursor does not change the behavior
of the application.
--
Armin

http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html

[Herfried K. Wagner [MVP]]

* "Bernie Yaeger" <be*****@cherwellinc.com> scripsit:

Is there a generic way to set up a waitcursor such that it will block
repress?

Why not disable the controls? This will give the user visual feedback
too.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Cor]

Did you see my post in the controls group about this?

Why not disable the controls? This will give the user visual feedback
too.

[Bernie Yaeger]

That's what I'm doing. Just thought there might be a better way.

Bernie
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:bq*************@ID-208219.news.uni-berlin.de...

* "Bernie Yaeger" <be*****@cherwellinc.com> scripsit:

Is there a generic way to set up a waitcursor such that it will block
repress?

Why not disable the controls? This will give the user visual feedback
too.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>