--- In [email protected], "swzoh" <sean...@...> wrote: > > --- In [email protected], "entropyreduction" > <alancampbelllists+yahoo@> wrote: > > > > but fails if trying to create a word app object, returning > > 0x8001010d "An outgoing call cannot be made since the application is > > dispatching an input-synchronous call" > This error can be avoided by checking first: > fBlocked = (InSendMessageEx(NULL)&(ISMEX_REPLIED|ISMEX_SEND)) == ISMEX_SEND > Make a COM call only when fBlocked is False.
Hmm. So I'm about to call a COM function, I do the check, find I'm blocked. So what then? I'm on the one and only Powerpro thread, sleeping probably won;t help much. Messages related to the link Sheri sent: http://www.codeproject.com/Messages/2932857/Re-ATL-Add-In-and-MFC-DLL-communication-problem.aspx suggest reverting to what I'm doing already: put my com stuff on its own thread. > Looks like PP receives a lot of SendMessage, which appears unusual to me. One > thing I can think of on this is PP's Hook. Did you happen to be using > HookWindowEvents and/or HookSystemEvents when testing? I think powerpro itself hooks just about everything? I'm on its main thread in versin I'm describing. > > CLSCTX_ALL instead of CLSCTX_SERVER does the same. > Better not use CLSCTX_ALL, it could interfere in creating local servers. Ok, thanks.
