Mouse Pointer Cursor and textbox

  • Thread starter Thread starter DotNetShadow
  • Start date Start date
D

DotNetShadow

Hi Guys,

I have been having this problem recently where I have a form with a
textbox and button, if in the button event I have the following:

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Me.Cursor = Cursors.WaitCursor
Textbox1.text = Now.Tostring
System.Threading.Thread.Sleep(2000) ' 2 second wait
Me.Cursor = Cursors.Arrow
End Sub

If I click the button the mouse cursor changes to an hourglass,
updates the textbox with current time and after 2 seconds the mouse
cursor returns back to the arrow The problem lies that when u click
the mouse button repeatedly even though the mouse cursor changes to an
hourglass the button is still clickable furthermore u can type text in
the textbox.

Is this the default behaviour of .NET? Is this a bug? I have even
tried disabling form elements and changing the cursor of these form
elements to hourlgass with no success can someone please help thanks

Regards DotNetShadow
 
DotNetShadow said:
If I click the button the mouse cursor changes to an hourglass,
updates the textbox with current time and after 2 seconds the
mouse cursor returns back to the arrow The problem lies that when u
click the mouse button repeatedly even though the mouse cursor
changes to an hourglass the button is still clickable furthermore u
can type text in the textbox.

Is this the default behaviour of .NET?
Click to expand...

This is the default behavior of Windows. Mouse and keyboard interaction and
other events have always been queued. Even in DOS there was a keyboard
buffer queueing the keyboard input.
 
Hi Roberto,

A question like this has been yesterday also in this newsgroup

the answer is make the textbox1.enabled = false

I hope this helps?

Cor
 
Cor said:
A question like this has been yesterday also in this newsgroup

the answer is make the textbox1.enabled = false
Click to expand...

I think you mean button1.enabled = false, but, this wouldn't help also. The
mouse clicks will be processed after the button has been enabled again.
 
Hi Armin,

I saw your answer, and please see my message about what I thought it was a
bug but you say normal behaviour.

Now I know that this behaviour is known, I did not know it, but I find it
weird, no user will understand it.

Thanks anyway

Cor
 
Thanks for all your replies guys, just afew follow up questions:

1) So if this is the default behaviour for windows in vb6 apps would
the same problem occur?

2) How do you get around the problem? Disabling a form element will
not help since after the event occurs the mouse messages continue so
how do you cancel them?

3) Can sample code be posted to solve this problem?


Regards DotNetShadow
 
DotNetShadow said:
Thanks for all your replies guys, just afew follow up questions:

1) So if this is the default behaviour for windows in vb6 apps
would the same problem occur?
yes

2) How do you get around the problem? Disabling a form element
will not help since after the event occurs the mouse messages
continue so how do you cancel them?

3) Can sample code be posted to solve this problem?
Click to expand...

Put the work in a different thread. Your UI thread will stay responsive. In
this thread, I usually show a modal Form showing the current process and the
progress (if possible). The Form also contains a cancel button.
 
Hi Armin,

If you see the test I did in this newsgroup with my question if it is bug.

I could not get the unwised behaviour when I disabled the textbox instead of
making it read only.

I was thinking on that later, maybe you can try it.

Cor
 
Cor said:
If you see the test I did in this newsgroup with my question if it is
bug.
Click to expand...

I thought I've already answered in the other thread. Now I looked again and
saw that my reply was still in the templates folder = not sent yet. I didn't
send it because I was unsure about the "message of your message". Well, I've
sent it now but it doesn't contain much, so.....
I could not get the unwised behaviour when I disabled the textbox
instead of making it read only.
Click to expand...
I was thinking on that later, maybe you can try it.
Click to expand...

I'll have a look.
 
Back
Top