>>That [out] has now become an __in because the caller allocates the buffer.
> If you are *implementing* this method - is there a problem at all? > The caller HAS already allocated the buffer, you only have to fill it. > Anyway, if you have special requirements that can not be fullfilled by > the 'high level' method implementation then you should use the 'low level' > implementation; I have posted several times about them. Yes, I'am implementing the event handler, and yes, as I tried to explain in the previous mail there is a problem as there is a mismatch between "reality" and the comtypes generated prototype. The argument is specified as [out] -as data is flowing from the implementation (callee) to the caller. That means for the (high-level) comtypes: the buffer never reaches my implementation of the event handler. As the buffer is preallocated by the caller that should really be interpreted as an [in] argument. I guess then, there is nothing else to do but to modify the generated file, or use the low-level stuff (but i really like high level... -That's why I used Python in the first place :) ) -- Regards Torbjørn Tyridal ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ comtypes-users mailing list comtypes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/comtypes-users
