Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Possible Threading situation
Message
From
15/03/2004 16:31:42
 
 
To
15/03/2004 03:36:25
General information
Forum:
ASP.NET
Category:
Other
Miscellaneous
Thread ID:
00885530
Message ID:
00886494
Views:
14
Kev,

>Although you've corrected my on my misconceptions about Modal forms (thank you)

You're welcome. =)

>I still need the form to be visible, and that's why I can't have the form hiding after the button has been clicked.

OK, I have another question for you. What do you do (or plan to do) with this form that it needs to remain open? Is it some kind of wizard that you're processing in steps? (I've done that sort of thing and just collected all the info for each step in a DataSet and then processed the data from the calling method, instead of processing each step of the wizard a step at a time). Anyway, you can re-show the form again I suppose, if you need to keep it showing.

Unfortunately, I have absolutely no experience with launching asynchronous threads (assuming that this is one way to handle this) and that's probably why I keep coming back to modal dialogs. Maybe someone else might jump in with some other suggestions.

~~Bonnie



>>Kevin,
>>
>>>I'll respond but I'm on my way out so if I don't respond until Monday - I'm not being unsociable :-)
>>
>>And I won't be around all weekend either, as I usually am, so other than today, I may not respond again until Monday either. =)
>>
>>> ... with a Modal form I have to wait until it is released - and that ain't no good.
>>
>>I'm wondering if you've got a few misconceptions about Modal Forms. First, it's not released when it's closed. It's simply hidden, so it still exists. You have to set each button's .DialogResult property to a DialogResult enum (so your Next button might be btnNext.DialogResult = DialogResult.OK and your Cancel button might be btnCancel.DialogResult = DialogResult.Cancel). That's all that's needed to make the form behave properly when it's called with MyForm.ShowDialog().
>>
>>Now, I know you said that you want the form to still be there when you're done with it, so maybe that's why you're opposed to a ModalForm, but since the form really still exists, you could simply display it again. As I said, it hasn't been closed, it's simply hiding.
>>
>>I know I'm being stubborn about this (trying to get you to use .ShowDialog()) and maybe you have other reasons for not wanting to do it this way ... if so, I guess I'll have to put on my thinking cap. But, at this point, it still sounds to me like a ModalForm would be ok and you're just missing a few things about how it works. Am I wrong?
>
>Hi Bonnie
>
>Although you've corrected my on my misconceptions about Modal forms (thank you) I still need the form to be visible, and that's why I can't have the form hiding after the button has been clicked.
>
>Thanks
>Kev
Bonnie Berent DeWitt
NET/C# MVP since 2003

http://geek-goddess-bonnie.blogspot.com
Previous
Reply
Map
View

Click here to load this message in the networking platform