[python-win32] OLE Server Busy dialog box

[Mark Hammond]

I can throw you a new win32uiole module with the functions referenced in the
knowledge base article, but apart from trying to fiddle with the main
thread's thread-state (search for 'sys.coinit_flags'), I can't offer much
more help...

Mark

> Some more details about the server busy dialog box.
>
> This program, that I'm working with, calls MakeActiveXClass(wxPython),
> which calls pywin.mfc.CreateControl, which calls
> win32ui.CreateControl. If I connect to a slow COM server just _before_
> the call to win32ui.CreateControl, then everything is fine, no busy
> message. But after the Control is created, it seems that the program
> gets in an "incorrect" state, i.e, whenever I call a slow COM server,
> _after_ CreateControl has been called, the busy message box will
> appears.
>
> is there perhaps any initialization that I may have forgotten, or any
> other ideas?
>
> Thanks a lot,
> Diogo
>
>
>
> 2006/8/4, Diogo <odiogo at kameruuh.eu>:
> > > Unless you are using the win32ui module, its unlikely you
> qualify as an "MFC
> > > COM client".
> >
> > I'm not using the win32ui. And this makes me wonder I would
> get this box.
> I was wrong at this point. The program is using win32ui.
>
> >
> > > | Another way to suppress the server busy dialog box is to use
> > > | OleInitialize and OleUninitialize instead of AfxOleInit in your
> > > | application.
> > >
> > > which are easy to call.
> > The program was using CoInitialize() only. Now it uses
> OleInitialize().
> > The "busy message" doesn't appear always, and with OleInitialize it
> > stopped appering in my computer. But while running in
> another computer
> > it still appears.
> >
> > BTW, there's no OleUninitialize. Should I use the Co one?
> >
> > Thanks for the help,
> > Diogo
> >
> _______________________________________________
> Python-win32 mailing list
> Python-win32 at python.org
> http://mail.python.org/mailman/listinfo/python-win32
>