From: MHammond at skippinet.com.au (Mark Hammond)
Date: Fri, 9 Apr 1999 11:15:02 +1000
Subject: COM Event Sinks and Connection Points in Python
References: <7eggfh$o0f$1@nnrp1.dejanews.com> <7egnl2$ca5$1@m2.c2.telstra-mm.net.au> <7eie3h$sr$1@newsin-1.starnet.net>
Message-ID: <7ejk9j$5tn$1@m2.c2.telstra-mm.net.au>
X-UID: 1593                                                  

Martin Bertolino wrote in message <7eie3h$sr$1 at newsin-1.starnet.net>...
>Some of COM features (especially when running in a Single Threaded
Apartment
>(STA)) depend on the application having an event loop. I have not looked at
>the sources for PythonWin, but I have looked at the Python ones, and I did
>not see any event loop servicing the event queue. This would explain why
you
>don't see the fired events.

I have tried that - although without a window (note pythoncom exposes enough
to run a message loop - win32event an even better one :)

Also tried running within Pythonwin (so it has a window), but not as a
control - still didnt work.  Seemed to need some of the control container
plumbing to be in place.

Dont think I tried all of the threading models tho...

Mark.






