When I generate the interface file for a COM object using makepy, it
generates an incorrect signature for one of the methods:
def ReadTag(self, Name=defaultNamedNotOptArg,
pBuf=defaultNamedNotOptArg, nOS=defaultNamedNotOptArg,
nWords=defaultNamedNotOptArg):
return self._oleobj_.InvokeTypes(9,
This just occurred to me -- I'll bet that is supposed to be a pointer to
an array of floats, isn't it? Then yes, you have a problem. That's not
the proper way to pass an array in COM. In the dispatch mechanism,
you're supposed to pass it as a safe array structure that contains
sizing
Ok! I'll install Visual Studio and see if I can make any headway.
Thanks for your help!
Brad
On Wed, Jan 26, 2011 at 5:44 AM, Graham Bloice
graham.blo...@trihedral.com wrote:
On 25/01/2011 06:44, Brad Buran wrote:
When I generate the interface file for a COM object using makepy
, 2011 at 9:21 PM, Mark Hammond skippy.hamm...@gmail.com wrote:
On 26/01/2011 3:38 PM, Brad Buran wrote:
I've been using win32com.client for the past year or so. Recently, I
noticed that there was a bottleneck in my code, and I tracked this
down to _get_good_single_object (line 478). When
