If I make the following change to oleargs.cpp
--- oleargs.cpp.orig2007-07-13 11:21:30.711416000 -0400
+++ oleargs.cpp 2007-07-13 11:22:46.764499200 -0400
@@ -834,6 +834,16 @@
if (FAILED(hres))
return PyCom_BuildPyException(hres);
long
(c.QueryInterface
(pythoncom.IID_IDispatch))
I think we could also argue this is a bug in win32com - it should
try and QI any IUnknown objects - but changing this might break
existing code...
Mark
-Original Message-
From: [EMAIL PROTECTED] [mailto:python-win32-
[EMAIL PROTECTED] Beh
On Jul 4, 2007, at 7:12 PM, Mark Hammond wrote:
>
>>
>> At this point f should be a 2048 by 1536 array of bytes, but
>> instead...
>>
> len(f)
>> 2048
> type(f)
>>
>
> Arrays of type VT_UI1 are returned as buffers. You should find the
> length
> of f is 1536, and you can treat it as
I'm making a COM call that should return a two dimensional array, but
instead I get back a buffer that appears to only contain a single row
from the array.
Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit
(Intel)] on
win32
Type "help", "copyright", "credits" or "license" f
I'm trying to use a COM library from python.
If I use dynamic dispatch, the com objects all behave correctly, but
the constants defined in the COM library don't show up.
If I use static dispatch, the constants show up, but COM objects
returned by calls into the COM library seem broken.
As
eras', '_ApplyTypes_', '__cmp__',
'__doc__', '
__getattr__', '__init__', '__module__', '__repr__', '__setattr__',
'_get_good_ob
ject_', '_get_good_single_object_', '_oleobj_',
