Re: message box non modal?
- From: "Jack" <notreplyto@it>
- Date: Sat, 6 May 2006 17:47:00 -0400
or set a flag to ignore them while the modal msgbox is up.
Thank you Tom.
That is what I have decided to do.
"Tom Esh" <tjeshGibberish@xxxxxxxxxx> wrote in message
news:k03q525s6l9v6v80mq2vpgi2a0dukmea5d@xxxxxxxxxx
On Sat, 6 May 2006 14:48:02 -0400, "Jack" <notreplyto@it> wrote:
My problem is, that my application receives callbacks from Windows.
Sometimes there is a a situation, when the msgbox is displayed (user has
not
reacted yet to it), but the callback is received and it tries to show
another window.
In that situaton there is Error 401: :Non modal form cannot be displayed,
when there is modal form opened".
So you've got a modal dialog (msgbox) that by nature limits UI input,
and callbacks that can change the UI. They aren't going to get along,
and if they somehow did, the user would certainly be confused.
The problem here is one of ~design~ consideration, in particular does
it really need to be modal (?) If it must be modal, then asynchronous
callbacks that can effect UI input are a no-no. In that case you
should either remove those aspects from the callbacks, or queue them,
or set a flag to ignore them while the modal msgbox is up.
-Tom
MVP - Visual Basic
(please post replies to the newsgroup)
.
- Follow-Ups:
- Re: message box non modal?
- From: Michael C
- Re: message box non modal?
- References:
- message box non modal?
- From: Jack
- Re: message box non modal?
- From: Martin
- Re: message box non modal?
- From: Jack
- Re: message box non modal?
- From: Martin
- Re: message box non modal?
- From: Jack
- Re: message box non modal?
- From: Tom Esh
- message box non modal?
- Prev by Date: Re: Tracing
- Next by Date: Re: Reading a file directly into an array
- Previous by thread: Re: message box non modal?
- Next by thread: Re: message box non modal?
- Index(es):
Relevant Pages
|
Loading