I'm afraid my only other idea is to contact the vendor of the other app
and see if they can shed any light on the problem...
Cheers,
Mark
On 30/04/2012 10:49 AM, reckoner wrote:
On 4/29/2012 3:48 PM, Mark Hammond wrote:
On 30/04/2012 1:07 AM, reckoner wrote:
Thanks for your reply.
Yes, t
On 4/29/2012 3:48 PM, Mark Hammond wrote:
On 30/04/2012 1:07 AM, reckoner wrote:
Thanks for your reply.
Yes, the app works fine if I don't PumpMessages in my own code. There is
no console that the application fires up when it runs the embedded
Python code. In this situation, how do I (or, can
On 30/04/2012 1:07 AM, reckoner wrote:
Thanks for your reply.
Yes, the app works fine if I don't PumpMessages in my own code. There is
no console that the application fires up when it runs the embedded
Python code. In this situation, how do I (or, can I?) pump for my own
messages if the applicat
Thanks for your reply.
Yes, the app works fine if I don't PumpMessages in my own code. There
is no console that the application fires up when it runs the embedded
Python code. In this situation, how do I (or, can I?) pump for my own
messages if the application is doing some other kind of event
I don't know why it crashes exactly, but if the other app has its own
event loop then things are going to get screwey - PumpMessages never
returns (well, not until a WM_QUIT message is received), so their event
loop will never run.
I'd guess that their event loop and event handlers have some a
I have written some code that catches windows events that also includes
the usual PumpMessages, and all of this works fine when I run it from
the Python interpreter (Python version 2.6). However, when a separate
application that has Python embedded calls the same code, the calling
applicatio
