vlax-put-property usage

I think that's what I said.

 

Think again.
What you said was "(vlax-invoke) handles
the results of multiple output parameters internally, and
always returns them as a list of results (and converts to
LISP types where appropriate)."

Technically you can claim correctness since nil can be an empty list.

 

John - I don't have to think again, I know exactly
what I said, and that's exactly what (vlax-invoke)
does.

Output parameters in ActiveX are the ones that
vlax-invoke-method requires quoted symbols for.

Internally, (vlax-invoke) receives output parameters
from the ActiveX server by passing it an array of
variants, which the server fills in with each output
value, and then (vlax-invoke) gets the value of each
of those variants and puts them into a list, which
it returns it as its result.

That's exactly what (vlax-invoke) does internally.

 

I'm sorry. I don't see where (vlax-invoke) is returning anything to 'MinPt or
'MaxPt in the example...
Command: (vlax-invoke Object 'GetBoundingBox 'MinPt 'MaxPt)
nil
Command: !minpt
nil
Command: !maxpt
nil

 

John - I don't believe I suggested that. You may be
misinterpreting what I was referring to by 'output
parameters'. These are ActiveX parameters, not LISP
function parameters. If an ActiveX method is declared
with output paraemters, the client that calls the
method must supply parameters to receive the output
(this is ActiveX, not LISP). (vlax-invoke) supplies
those parameters internally when it calls an ActiveX
method that takes output params.

Then it takes the values of those parameters and
converts to LISP types, returns them in a list.

 

So where are the returns?

 

At the IRS

Sorry, this has degraded to gibberish and that's where I get off.

 

I'm not sure I agree. The naming convention of all
vla-* functions is consistent. vla-get-<propertyname>
and vla-put-<propertyname> are fairly consistent.

However, there is one caveat about this, which is
when a method's name begins with the string "Get"
(e.g., vla-GetInterfaceObject and vla-GetAttributes
for example).

To make my point, just search google on either of
the following, and you'll see how many times I and
others have incorrectly used them:

vla-get-interfaceobject
vla-get-attributes