Re: [python-win32] DispatchWithEvents design question

2007-06-07 Thread Mark Hammond
> BTW, my offer of an example still stands and I think I may > finally have > enough of an understanding to post something if it would be helpful to > others. That would be most welcome - I'd be happy to include in pywin32 and obviously you could put if anywhere else that takes your fancy... Chee

[python-win32] path to py2exe-generated package

2007-06-07 Thread TK Soh
My program uses some custom icons and data that are locate in a subdir within the program root. However, when executing the package created by py2exe, the program was not able to access these icons and data through relative paths. Any advice on how to handle this would be greatly appreciated. Thank

Re: [python-win32] DispatchWithEvents design question

2007-06-07 Thread Tim Roberts
Richard Bell wrote: > Is it then the case that my OnEvent routines should only execute under one > of the following conditions? > > 1 - I interact with the COM target as in ie.Visible = 1 or ie.Navigate2 > 2 - I execute a pythoncom.PumpWaitingMessages > I believe this to be true. You are apart

Re: [python-win32] DispatchWithEvents design question

2007-06-07 Thread Richard Bell
Tim Roberts wrote |It's quite possible for a single callback to happen both synchronously |and asynchronously, depending on context. In this case, IE probably |considers the StatusBar to be one of its "commands", so the |OnCommandStateChange makes some sense. Is it then the case that my OnEvent r

Re: [python-win32] DispatchWithEvents design question

2007-06-07 Thread Tim Roberts
Richard Bell wrote: > I rewrote the test, see below. When run it behaves as you suggest (see the > test output below). In particular the OnVisible event occurs synchronously > before return from 'ie.Visible = 1' as you suggested. I checked StatusBar > and it appears to be synchronous as well. I

Re: [python-win32] DispatchWithEvents design question

2007-06-07 Thread Richard Bell
Tim Roberts wrote |These are synchronous events. That is, these events are generated |directly by the requests you made. I believe you will find that the |"OnVisible" callback occurs before "ie.Visible = 1" returns. It's being |handled by that same thread, which is suspended waiting for IE to