winforms - How can I make a 'Partially' modal dialog? -


Is there a way to start showing the dialog, but then instead of hiding it, keeping it visible while changing it is a non- For modal communication?

I show dialogue, block the method showing the dialogue. Then, when the user clicks the 'Finnish' button on the dialog I want to:

  • The dialog to be visible.
  • Control to return to the method shown in the dialog.

I have achieved this result by running a dialogue on a different STA thread, and using an event, block the main UI thread until the 'finish' is pressed, but in this method one Grip: When the dialog appears, you can click on the closest button of the main window, and the main window closes when the dialog is hidden.

Updates

Thanks to the responses so far. Sorry - it seems that I am very much in the middle of the background and not enough.

This form is effectively a modal 'wizard' dialog - it appears, mainly sits in front of the main app, and then hidden. So far as the user is concerned, there is no non-standard oddity. The only difference is that the dialog is inspired by a series of callbacks from the UI thread, so I think it will work to make the model really realistic for its lifetime (by calling Shoddyogy). The first callback should show the dialog, and then the user must block their preferences when setting them through the dialog UI. After that, the dialog remains visible and displays a progress bar page while many other callbacks are created from the UI threads. Eventually the look is hidden, the user is not interacting with the main window, while the form is up. As far as they are concerned, this 100% modal wrt should be the main UI thread.

(This is a dialog for a visual studio wizard - it is operated from a series of callbacks UI threads) To show an option dialogue, hide it, instead of immediately making a "biggest progress" Show the form and then hide it, but I think displaying a dialog is a comfortable experience for the user.

Again - sorry for the confusion!

Perhaps you want to think about your interaction model again? How would you explain this to your users? They have a program that works in a computer program and is a good reason to break it in a better way. They know about the modal dialogue, they know about non-modal communication, they know about the inspectors. Choose one, and apply it

The model dialog is used for short-term contact. They should not stop getting out of the application. User is in the control of interaction, the program only requires minimal restrictions.

[What is wrong to show progress bar in the modal dialog] after the explanation? After clicking on the OK button start processing, disable all buttons, just cancel the cancel button? If it takes a long time, then the user may want to cancel the operation. Close the dialog when the processing is finished.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -