Instead
of using MessageDlg, make a form off your own to display the message. Instead
of Form.ShowModal, go Form.Show. This will allow control back to your mainform.
In the mainform you will be able to trap all the events, and send focus back to
the message form etc. There is an api call (FlashWindowEX) that flashes a
window also, which might bring attention to the form for the users.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf
Of [EMAIL PROTECTED]
Sent: Tuesday, 1 April 2003 8:07
am
To: Multiple recipients of list
delphi
Subject: RE: [DUG]: Windows quirks
and inexperienced users
Thanks
Nello, I think I understand what you're saying, but I'm unsure how to
accomplish this.
What
happens is that when I do an automatic email (from within my app), my screen
changes to the Outlook screen. (XP brings up messages warning that a program is
using Outlook and it could be a virus etc). Then my program does a MessageDlg('fax
now sent to fax queue'.... Command. However, now the focus is on Outlook, so a
task item for the dialog is created on the task bar. If I go to the task bar
and click on my main app icon (not on the dialog task), then it
"appears" as though my app has bombed when in fact the MessageDlg is
sitting on the task bar waiting to be Ok'ed.
Any
ideas?
Thanks.
Dave Jollie
Tower NZ IT
09 368 4259
-----Original Message-----
From: Nello Sestini
[mailto:[EMAIL PROTECTED]
Sent: Friday, 28 March 2003 2:48PM
To: Multiple recipients of list
delphi
Subject: Re: [DUG]: Windows quirks
and inexperienced users
if i'm following this
correctly, i think the problem is that the
"fax sent... "
dialog is modal - so it blocks all keystroke/mouse input
sent to the main window
of the app.
one way to get around
this (if it's your app) is to make that dialog
modeless - and then
enforce the "modal" features that you want (for example
not allowing the user to
do anything else until they cancel the dialog).
If the dialog is modeless
- then taskbar clicks and attempts to click
into the main application
window will work as expected.
----- Original Message -----
Sent: Friday,
March 28, 2003 09:32
Subject: [DUG]:
Windows quirks and inexperienced users
Hi all
I have a mail merge app which has a
button for sending off a letter as a fax to the client. It has a dialog which
comes back at the end of the process, saying "Fax sent to fax queue".
In some instances, inexperienced
users (not familiar with Windows) have sidetracked off to e.g. read an email,
and then clicked back on the task bar item for the letters program again. When
they try to exit the program, and it doesn't respond, they use ctrl-alt-delete!
But if they'd looked on the task bar, they would have found another entry,
which was the "Fax sent to fax queue" dialog, still waiting for the
"OK" to be clicked.
How do I help them out? Is there a
way to change the behaviour of Windows, so that when clicking on a parent form,
if there is a child form / dialog still outstanding (not dealt with), then it
re-focuses to this? I'm new to Windows programming, so this may be a silly or
easy question.
Also, is it easy to trap the ctrl-alt-delete
event and give a controlled response to the users desire to kill my app?
Any suggestions appreciated. TIA.
Dave Jollie
Tower NZ IT
09 368 4259
