> That's exactly what I ended up doing. I guess I was just a little too
> green to do it right the first time. I didn't know how to pass a SAFEARRAY
> correctly, so I thought I'd hide the problem and put it in a VARIANT :-)
>
> Strangely, this actually worked for my C++ clients.
Best I can tell,
> I've gotten right down to the problem. Has nothing to do with the
> number of
> parameters. One of the parameters is of type VT_VARIANT (0x000c). That
> variant
> type is not supported by the function PyCom_PyObjectFromVariant, which
> gets
> called along the chain of getting the values down to P
> I have implemented an object that supports connection points in COM.
>
> In ATL, there is a #define that limits the number of parameters
> supported for a
> connection point client:
>
> #define _ATL_MAX_VARTYPES 8
>
> I have one function that has 11 parameters, so for my C++ client (using
> AT
I have implemented an object that supports connection points in COM.
In ATL, there is a #define that limits the number of parameters supported for a
connection point client:
#define _ATL_MAX_VARTYPES 8
I have one function that has 11 parameters, so for my C++ client (using ATL) I
had to redefine
