Re: [python-win32] VT_UI1 ByRef behavior

2007-05-10 Thread Kevin Patterson
In case anyone else is interested, below is the code I ended up using to filter buffers from the input and output of the com. It makes use of the Python2.4 decorators that are added to all the functions in th py file generated by makepy. I never thought I would find a reason for the decorator,

Re: [python-win32] VT_UI1 ByRef behavior

2007-05-09 Thread Kevin Patterson
Alrighty, I'll keep looking in to it. I think it is easy to make the buffers get returned as a python list. Almost all the code exists to help with that. The tough part is telling the COM that the array being passed IN needs to become a Safe Array where the size of each element is only VT_UI1.

Re: [python-win32] VT_UI1 ByRef behavior

2007-04-29 Thread Mark Hammond
I was curious is there a way to prevent an array of VT_UI1's from being converted to a buffer? Or perhaps a way to modify the file generated from makepy to prevent the conversion? Nope, no such facility exists. Feel free to propose a patch though. Cheers, Mark

[python-win32] VT_UI1 ByRef behavior

2007-04-28 Thread Kevin Patterson
I was curious is there a way to prevent an array of VT_UI1's from being converted to a buffer? Or perhaps a way to modify the file generated from makepy to prevent the conversion? I am working with a COM module that uses the VT_UI1 and ByRef for a LOT of its input/output, but it's a bit of a