[RESOLVED] How to UseWaitCursor correctly
CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 15 of 40

Thread: [RESOLVED] How to UseWaitCursor correctly

Threaded View

  1. #16
    Join Date
    Jun 2010

    Re: How to UseWaitCursor correctly

    Quote Originally Posted by Arjay View Post
    The screen shot doesn't already have a cancel button. What you have is a close button (i.e the 'X' button).
    Ah, yes, of course, sorry... The screen shot you are referring to is a few versions of the app back. I have attached a current one to this post. (I hope this doesn't look like image overkill la firoz.raj now. )

    You can disable the 'X' button. Not sure how off the top of my head, but I'll look in google in a minute.
    Sorry again: I just posted that I found the solution for that issue (including the solution itself) 11 minutes before your post I'm just replying to. Looks like we encountered some kind of synchronisation problem here. Maybe we should use some kind of semaphore or the like? I hope you read this one in time before you waste any time.

    The user prompt to verify canceling isn't like a "are you really sure?". It's pretty much the standard when cancelling a long running operation in this manner. If you don't have it, your users will be pissed when they thought the 'X' would merely hide the progress dialog.
    I 100% agree when it comes to the X button. But is this really appropriate (or even required) for a button explicitly labelled "Cancel"?
    Attached Images Attached Images  

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Windows Mobile Development Center

Click Here to Expand Forum to Full Width

On-Demand Webinars (sponsored)