Reliable way to change the cursor

[Luke R]

1) Me.Cursor = Cursors.WaitCursor
This works - except when you hover the mouse over a textbox or datagridview
control, it doesnt show the waitcursor.

2) Me.UseWaitCursor = True
This works if i set it off a button click. It does not work if i set it as
part of a process, which is extremely odd.
One would suspect that would be because im unsetting it somewhere in the
process, but to eliminate this possibility, i did a replace and changed them
to the Me.Cursor method and it worked fine. Of course, its not fine because
of the problems i described in #1.

Anyone else had this issue?

[Armin Zingler]

"Luke R" <do**@spam.meschrieb

1) Me.Cursor = Cursors.WaitCursor
This works - except when you hover the mouse over a textbox or
datagridview control, it doesnt show the waitcursor.

2) Me.UseWaitCursor = True
This works if i set it off a button click. It does not work if i set
it as part of a process, which is extremely odd.
One would suspect that would be because im unsetting it somewhere in
the process, but to eliminate this possibility, i did a replace and
changed them to the Me.Cursor method and it worked fine. Of course,
its not fine because of the problems i described in #1.

Anyone else had this issue?

Why not use Cursor.Current= Cursors.Waitcursor?
Armin

[Luke R]

At first i thought that didnt even work at all, and then i discovered that
it works if you dont touch the mouse... if you move the mouse one pixel in
any direction it goes back to the default cursor for the object the cursor
is over.
"Armin Zingler" <az*******@freenet.dewrote in message
news:Og**************@TK2MSFTNGP05.phx.gbl...

"Luke R" <do**@spam.meschrieb

>1) Me.Cursor = Cursors.WaitCursor
This works - except when you hover the mouse over a textbox or
datagridview control, it doesnt show the waitcursor.

2) Me.UseWaitCursor = True
This works if i set it off a button click. It does not work if i set
it as part of a process, which is extremely odd.
One would suspect that would be because im unsetting it somewhere in
the process, but to eliminate this possibility, i did a replace and
changed them to the Me.Cursor method and it worked fine. Of course,
its not fine because of the problems i described in #1.

Anyone else had this issue?

Why not use Cursor.Current= Cursors.Waitcursor?
Armin

[Armin Zingler]

"Luke R" <do**@spam.meschrieb

At first i thought that didnt even work at all, and then i
discovered that it works if you dont touch the mouse... if you move
the mouse one pixel in any direction it goes back to the default
cursor for the object the cursor is over.

Works here. I assumed that the WaitCursor only makes sense if the thread is
busy. Then it should work. If it is not busy, or if you use
Application.Doevents, then it does not work, but then one shouldn't use the
WaitCursor (IMO).
Armin

[Luke R]

Am i confused or are you saying that you shouldnt use the WaitCursor if you
are using DoEvents?

It works if the ui thread is locked (i.e. running a process). But what about
if i want to write status messages to the status bar during the process? The
only way to make them display is by calling DoEvents.
This really pisses me off. Why cant things just work the way they say they
do. Especially with something as fundamental as the wait cursor.

UseWaitCursor: "Gets or sets a value indicating whether to use the wait
cursor for the current control and all child controls."

That is false. It simply doesnt work like that.
"Armin Zingler" <az*******@freenet.dewrote in message
news:ed**************@TK2MSFTNGP04.phx.gbl...

"Luke R" <do**@spam.meschrieb

>At first i thought that didnt even work at all, and then i
discovered that it works if you dont touch the mouse... if you move
the mouse one pixel in any direction it goes back to the default
cursor for the object the cursor is over.

Works here. I assumed that the WaitCursor only makes sense if the thread
is
busy. Then it should work. If it is not busy, or if you use
Application.Doevents, then it does not work, but then one shouldn't use
the WaitCursor (IMO).
Armin

[Armin Zingler]

"Luke R" <do**@spam.meschrieb

The reason the wait cursor is important is because my application
communicates with the database via a web service. Running operations
on a background process is not always practical, so when I do need
to wait for a web service call to return, I need the cursor to be
the wait cursor. Sometimes I run multiple web service calls in a
row, meaning I need to update status messages along the way. The
only reason I use DoEvents is because I need the status label to
update...

I understand, but the point is: You use Doevents, consequently the user can
use the Forms and Controls. Why do you /still/ want to show a Waitcursor
because the user does /not/ have to wait. If you wanna show that there is
something going on in the background, show it in a label or put an animated
gif on the Form. Though, how do you handle it that the user can even close
the Form while waiting for the web service?

Armin