The problem was actually that the COM interface had not been fully
implemented. The API was just bouncing back input. The COM server is not
mine, I am just required to write code against it. The fact that this API
was not fully implimented was not apparent until I started delving into the
VB code of the server.
Communication here is not at an all time high :)
The few things I did figure out is that if the API has [in, out] params,
where in is never actually used, you can just send it junk and it will
return the values as it normally does.
retval, return1, return2 = o.testFunc(realval, junkval1, junkval2)
Where real val is a required input or an [in], and junkval1 and junkval 2
are [in, out] and meant to return data. retval has the HRESULT and return1
has the return data from the junkval1 [in, out] and return2 has the returned
data from the junkval2 [in,out].
Might be obvious to some, but for those of us just trying to make heads or
tails of COM programming, the subtlties in things like this can get you.
From: Tim Roberts <[EMAIL PROTECTED]>
To: Python-Win32 List <python-win32@python.org>
Subject: Re: [python-win32] using a COM interface with [in, out]
Date: Wed, 24 Jan 2007 17:47:14 -0800
Rex Corrovan wrote:
> Nevermind, I am an idiot, figured out my problem. Sorry to bother.
What was the problem? You can help the next guy trying to do this.
--
Tim Roberts, [EMAIL PROTECTED]
Providenza & Boekelheide, Inc.
_______________________________________________
Python-win32 mailing list
Python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
_________________________________________________________________
From predictions to trailers, check out the MSN Entertainment Guide to the
Academy Awards®
http://movies.msn.com/movies/oscars2007/?icid=ncoscartagline1
_______________________________________________
Python-win32 mailing list
Python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
