Re: Automation timeout problem

From:

"David Ching" <dc@remove-this.dcsoft.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Thu, 3 Jan 2008 17:51:29 -0800

Message-ID:

<wkgfj.2781$pr6.658@nlpi070.nbdc.sbc.com>

"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:l4uqn3d2h3m338omj40t6n71rschami60l@4ax.com...

I have a program which is using the Automation Interface to PowerPoint. If
I choose the
option to save a presentation, and execute CPresentation::Save, the save
takes some time
(the PowerPoint presentation is large). The result is the user gets an
annoying and
potentially confusing notification that the operation is failing because
the target is not
responding, and options are to retry or switch to. Of course, switch to
won't work
because PowerPoint is busy saving. Is there any way to (a) disable this
annoying message
(b) explicitly set the timeout (c) detect it is going to occur and
intercept it (short of
CBT hooks). This seems to be some intrinsic failure in the design of the
interface,
because it doesn't actually notice the controlled app is actually doing
what is requested.

// Disable the "Not Responding"/"Server Busy" dialog box, which is
displayed if a keyboard
// or mouse message is pending during an OLE call and the call has timed
out
AfxOleGetMessageFilter()->EnableNotRespondingDialog(FALSE);

// Disable the "Server Busy" dialog box from appearing after the COM call
times out.
AfxOleGetMessageFilter()->EnableBusyDialog(FALSE);

-- David