36 lines
1.2 KiB
Plaintext
36 lines
1.2 KiB
Plaintext
From: martinb at talx.com.no.spam (Martin Bertolino)
|
|
Date: Thu, 8 Apr 1999 09:19:01 -0500
|
|
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>
|
|
Message-ID: <7eie3h$sr$1@newsin-1.starnet.net>
|
|
X-UID: 1436
|
|
|
|
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.
|
|
|
|
Martin
|
|
|
|
Mark Hammond wrote in message <7egnl2$ca5$1 at m2.c2.telstra-mm.net.au>...
|
|
>
|
|
>cingram at my-dejanews.com wrote in message
|
|
><7eggfh$o0f$1 at nnrp1.dejanews.com>...
|
|
>>I am trying to use functionality from a DLL that requires me to create a
|
|
>COM
|
|
>>event sink so that it can call back with events. I am trying to write
|
|
this
|
|
>
|
|
>There appears to be some problem using connection points from Python.exe.
|
|
>
|
|
>Events seem a black art. Im happy to help you track this down, but I
|
|
havent
|
|
>much time...
|
|
|
|
|
|
|
|
|
|
|
|
|