That is awesome - thanks very much. It works as advertised (although
there was one trivial problem in the patch when generating COM objects
that I fixed.)
It works just fine with a py2k build, so all I need to do it integrate
the changes Roger made for py3k into the mix and we are in a much
2011/4/14 Mark Hammond skippy.hamm...@gmail.com:
Sadly some hacks were made to SWIG to support some of the COM objects and
the source to those changes were lost many years ago - this needs to be
revisited before we can upgrade. I haven't put much thought into that yet
but I'm sure something
Hi
2011/4/14 Mark Hammond skippy.hamm...@gmail.com:
Yeah - this is a bug in the general DWORD handling in SWIG generated files.
I'm not sure how to tell SWIG to use a different format char, but I have
managed to work around it in other ways which is good for the general case.
With the old
On 14/04/2011 4:55 PM, Amaury Forgeot d'Arc wrote:
Was it ever considered using a newer version of Swig?
Sadly some hacks were made to SWIG to support some of the COM objects
and the source to those changes were lost many years ago - this needs to
be revisited before we can upgrade. I
On Wed, Apr 13, 2011 at 11:55 PM, Mark Hammond skippy.hamm...@gmail.comwrote:
Yeah - this is a bug in the general DWORD handling in SWIG generated files.
I'm not sure how to tell SWIG to use a different format char, but I have
managed to work around it in other ways which is good for the
On 13/04/2011 2:14 AM, Chris Frantz wrote:
Hello,
I'm having a bit of trouble with ReportEvent: When I use a large value
for eventID, I get an OverflowError.
import win32evtlogutil
win32evtlogutil.ReportEvent('FooBar', 0xc0004652)
Traceback (most recent call last):
File stdin, line 1,
Hello,
I'm having a bit of trouble with ReportEvent: When I use a large value for
eventID, I get an OverflowError.
import win32evtlogutil
win32evtlogutil.ReportEvent('FooBar', 0xc0004652)
Traceback (most recent call last):
File stdin, line 1, in module
File
