Re: [python-win32] Fixing type ID for an interface file generated by makepy

2011-01-26 Thread Brad Buran
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, it

Re: [python-win32] Fixing type ID for an interface file generated by makepy

2011-01-25 Thread Tim Roberts
Tim Roberts wrote: Brad Buran wrote: 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,

Re: [python-win32] Fixing type ID for an interface file generated by makepy

2011-01-25 Thread Brad Buran
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

[python-win32] Fixing type ID for an interface file generated by makepy

2011-01-24 Thread Brad Buran
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,