> I've seen this myself, but couldn't reliably reproduce it.
> If I recall, allocating a new console, and then immediately
> freeing it seemed to clear the 'in-between' state.
Man, that did the trick! Thanks! I added a win32console.AllocConsole()
before the FreeConsole() in the first try-except-c
On Mon, Oct 6, 2008 at 11:12 PM, Joe Healy <[EMAIL PROTECTED]>wrote:
> Roger Upole wrote:
>
> Which Python version are you working with ?
>> I have an installer built from current CVS for Python 2.5 (32 bit), but
>> can create one for a different version when time permits.
>>
>>
> We are working
You can "try" using CreateToolhelp32Snapshot(TH32CS_SNAPPROCESS, 0); and
Process32First(snapshot, &process_entry);
I have had some success with this but sometimes this also could not recognize a
running process.
I am new to Python so am not sure if this available through python's windows API
-
Stian wrote:
> > I've seen this myself, but couldn't reliably reproduce it.
> > If I recall, allocating a new console, and then immediately
> > freeing it seemed to clear the 'in-between' state.
>
> Man, that did the trick! Thanks! I added a win32console.AllocConsole()
> before the FreeConsole()
Try passing pythoncom.Empty for the out param - that will provide a VT_EMPTY
param to the object, which it will hopefully accept and fill with the
result.
Mark
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Greg Antal
Sent: Tuesday, 7 October 2008 4:10 AM
To: python-win32@py
