"Nobody" <nob***@nobody.com> wrote in message
news:i43ift$ttu$1@speranza.aioe.org...
> "phil hunt" <a@abc.com> wrote in message
> news:i43f9i$k9b$1@speranza.aioe.org...
>>I have an application that pop up a form (vbModal) asking for password in
>>order to proceed. It pops up after a period of idling. It works prettty
>>well.
>> The hassle comes when there is a MsgBox popping up and the user does not
>> respond, then the modal form pop up. Now I got 2 modal things, and you
>> cannot click anything to move on. I have been sidestepping the problem by
>> disabling the modal form whenever I show msgbox. I am wondering if there
>> is a better way to do this.
>
> Do you have any minimized windows, even hidden background ones? Try
> calling this routine before showing the password form and MsgBox:
>
> Public Declare Sub OutputDebugString Lib "kernel32" Alias _
>    "OutputDebugStringA" (ByVal lpOutputString As String)
>
> Public Sub PrintAllMinimizedForms()
>    Dim frm As Form
>
>    For Each frm In Forms
>        If frm.WindowState = vbMinimized Then
>            DebugPrint "PrintAllMinimizedForms: " & frm.Name
>        End If
>    Next
>
> End Sub
>
> Public Sub DebugPrint(ByRef s As String)
>    Debug.Print s
>    OutputDebugString s & vbCrLf
> End Sub
>
> Use the following software to view the output when running in the EXE:
>
> DebugView:
> http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
>
> One similar problem I had is when showing a prompt, it would be out of
> focus. It turned out that I had a background form that is hidden and
> minimized. The form was minimized to save memory. Just by making it
> minimized, my app Mem Usage in Task Manager stays at 4 MB, instead of 10
> MB, even when the form is hidden in both cases. The Form was used as a
> Winsock host. If I don't minimize it, then the problem disappears.
> Eventually I had to use ForceForegroundWindow() function, but I don't like
> this solution as MS would probably block it some day:
>
> http://vb.mvps.org/samples/ForceFore/
>
> If you had no luck, can you post code that duplicates the problem?
>
>

"Larry Serflaten" <serfla***@gmail.com> wrote in message
news:i447oj$p52$1@news.eternal-september.org...
>
> "phil hunt" <a@abc.com> wrote
>> I have an application that pop up a form (vbModal) asking for password in
>> order to proceed. It pops up after a period of idling. It works prettty
>> well.
>> The hassle comes when there is a MsgBox popping up and the user does not
>> respond, then the modal form pop up. Now I got 2 modal things, and you
>> cannot click anything to move on. I have been sidestepping the problem by
>> disabling the modal form whenever I show msgbox. I am wondering if there
>> is
>> a better way to do this.
>
> How are you detecting idle time?  If that is on a Timer, why not just
> disable the
> timer before you show the msgbox?  You might wrap that up in a routine so
> as
> to catch it every time:
>
> Sub SimplePrompt(Msg As String, Optional Buttons As VbMsgBoxStyle =
> vbOKOnly)
>  Timer1.Enabled = False
>  If frmPassword.Visible Then
>    Unload frmPassword
>    MsgBox Msg, Buttons
>    frmPassword.Show vbModal
>  Else
>    MsgBos Msg, Buttons
>  End If
>  Timer1.Enabled = True
> End Sub
>
>
> LFS
>
>