RE: problems with arguments in executecommand method

Date : Thu, 27 Sep 2007 21:36:58 +0100
To : <XSI(at)Softimage.COM>
From : "kim aldis" <xsi(at)kim-aldis.co.uk>
Subject : RE: problems with arguments in executecommand method

No. Sorry, that was a mis-type following me messing around with the code. It actually fails as follows:-

 

CValue outArg;

CValueArray inArgs;

inArgs[0] = CValue( oUVSpace.GetFullName() );

Application().LogMessage( L"Args " + inArgs[0].GetAsText() );

 

Application().ExecuteCommand( L"ApplyKA_UVGrid", inArgs, outArg );

 

 

From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On Behalf Of Stephen Blair
Sent: 27 September 2007 21:26
To: XSI(at)Softimage.COM
Subject: RE: problems with arguments in executecommand method

 

inArgsB versus inArgs ?

 


From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On Behalf Of kim aldis
Sent: Thu 27 September 2007 4:03 PM
To: XSI(at)Softimage.COM
Subject: problems with arguments in executecommand method

Calling ExecuteCommand as below, the argument I’m giving it is appearing as Null in the history pane. oUVSpace  is a uvspace and I know it’s valid and of the correct type. Ring any bells with anyone?

 

Cheers.

 

ValueArray inArgs;

inArgs[0] = CValue( oUVSpace.GetFullName() );

Application().LogMessage( L"Args " + inArgs[0].GetAsText() );

 

Application().ExecuteCommand( L"ApplyKA_UVGrid", inArgsB, outArg );

 

 

 


Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.