Displaying wait cursor in while backgroundworker is running

后端 未结 9 1694
傲寒
傲寒 2020-12-30 03:50

During the start of my windows application, I have to make a call to a web service to retrieve some default data to load onto my application. During the load of the form, I

相关标签:
9条回答
  • 2020-12-30 03:58

    Don't display a wait cursor for this - instead, use a control on your form to indicate that the backgroundworker is busy doing something. The wait cursor is an appropriate indicator for the UI thread to use (since it indicates that the user can't/shouldn't touch anything), but it's not appropriate for something happening in the background.

    0 讨论(0)
  • 2020-12-30 03:58

    The Microsoft Reference Source gives us the implementation of Control.UseWaitCursor and Control.Cursor. If you examine Control.Cursor, you'll see that if UseWaitCursor is set to True, Control.Cursor returns Cursor.WaitCursor regardless of what cursor is set on the control. Because of this behavior, the value returned from Control.Cursor can't be cached.

    // DON'T DO THIS: THIS CODE WILL BREAK IF UseWaitCursor IS SET TO TRUE
    // Store the original cursor
    Cursor cachedCursor = this.Cursor;
    
    // Set the cursor to a wait cursor.
    this.Cursor = Cursors.WaitCursor;
    
    // Perform some task
    
    // Restore the original cursor
    this.Cursor = cachedCursor;
    

    While the above looks harmless enough, it can instantly lead to problems if someone sets Control.UseWaitCursor to True before it is executed. The result of which would be a stuck wait cursor due to Control.Cursor returning Cursors.WaitCursor on the first line in the above. A better method for changing the cursor is thus:

    // Change the cursor as needed
    this.Cursor = Cursors.WaitCursor;
    
    // Perform some task
    
    // Restore the default cursor when finished.
    this.Cursor = this.DefaultCursor;
    

    For the vast majority of things, the above should be sufficient to show a wait cursor when needed. However, if a child of a control also modifies the cursor, the cursor set by the child will override that which is set on the parent. IE if you set the cursor of a label to Cursors.IBeam on a form which sets its cursor to Cursors.WaitCursor, the label will display an IBeam while the form displays the WaitCursor. Only controls where Control.Cursor returns the same value as Control.DefaultCursor will display the WaitCursor set on the form in this case. This is where Control.UseWaitCursor comes in. Setting UseWaitCursor on a form sets UseWaitCursor on all of its children as well. As long as none of the controls on the form are using the broken code above. The DataGridView is only one of the many controls that used the broken code above.

    But.. what if you don't want a WaitCursor and want to maintain the cursor set externally by a user of your control? In this case, your options are limited, you must override the Cursor property of your control to receive the cursor set by a user of your control OR you must use reflection to gain access to the internal cursor value stored by the base Control class. Then, and only then can you use the first method above for caching and restoring the cursor. *Note: you must cache the internal cursor value set by the user of your control, not the result from base.Cursor!

    0 讨论(0)
  • 2020-12-30 03:58

    Here is what I'm doing now, I hope this help.

    private void LoadWaitCursor()
    {
        this.Dispatcher.Invoke((Action)(() =>
        {
            Mouse.OverrideCursor = Cursors.Wait;
        }));
    }
    private void LoadDefaultCursor()
    {
        this.Dispatcher.Invoke((Action)(() =>
        {
            Mouse.OverrideCursor = null;
        }));
    }
    
    0 讨论(0)
  • 2020-12-30 04:00

    In the MS forums thread UseWaitCursor not working but Cursor = Cursors.WaitCursor does../ & Cursor.Current vs. this.Cursor

    it was confirmed that WF's implementation of UseWaitCursor missed an opportunity to make it actually work to show an hourglass cursor and shown the HourGlass class, that can be used with "using" block

    using (new HourGlass()) {
            // Do something that takes time...
            System.Threading.Thread.Sleep(2000);
          }
    
    0 讨论(0)
  • 2020-12-30 04:01

    In WPF, I've done this by setting the Mouse.OverrideCursor property to Cursors.Wait before I start the Backgroundworker, and then resetting it to null in the RunWorkerCompleted event. Seems to work pretty well so far.

    public void go()
    {
        BackgroundWorker thread = new BackgroundWorker();
    
        thread.DoWork += run;
        thread.RunWorkerCompleted += taskCompleted;
        thread.WorkerReportsProgress = true;
    
        // Change mouse cursor to busy
        Mouse.OverrideCursor = Cursors.Wait;
    
        thread.RunWorkerAsync();
    }
    
    private void taskCompleted(object sender, RunWorkerCompletedEventArgs e)
    {
        // Reset mouse cursor
        Mouse.OverrideCursor = null;
    }
    
    0 讨论(0)
  • Does UseWaitCursor work? (Set to true when calling RunWorkerAsync(), and false when the completion event is called). What are you using to set the cursor now?

    0 讨论(0)
提交回复
热议问题