Why will the hourglass (WaitCursor) stop spinning?

Question

I have a button click code:

try { Cursor = Cursors.WaitCursor; GenerateReports(); } finally { Cursor = Cursors.Default; GC.Collect(); GenPacketBtn.Enabled = true; } 

Nowhere, but in the finally block, the cursor returns to default, but it "gets tired" and for some reason returns to its default state. Why is this the case and how can I assure him that he will not stop "waiting" until the big dad of all processes has completed (GenerateReports ())?

Answer 1

Use Control.UseWaitCursor = true instead, this is not a timeout.

If an expensive operation is performed, then Windows will prevail and it will change Cursor.WaitCursor to what it considers necessary. Thus, using Cursor.WaitCursor, it will be either due to the timeout (but not completely sure of it), or because Windows simply requires the right to own the cursor, regardless of its previous state. We also had a similar situation where the Cursor did not behave as expected when performing an expensive task that included third-party PDF converters, but we did not investigate more about the nature of the problem, since this was not a priority.

After a little reading, it turned out that the Hourglass cursor is a bit more complicated than it seems:

.NET WaitCursor: how hard is it to show an hourglass?

Also as a side note: you should use Cursor.Current = Cursors.WaitCursor , as this causes the cursor to instantly switch to a lesson, more information can be found at: fooobar.com/questions/103385 / ...