David,
There are a couple of answers for you. First, the API documentation
has sometimes lagged our features, so I suspect we just left this out.
You can work with design files through the API....
void ReadApplyDESFile( const string & in file_name )
void WriteDESFile( const string & in file_name )
void ReadApplyXDDMFile( const string & in file_name )
void WriteXDDMFile( const string & in file_name )
int GetNumDesignVars()
void AddDesignVar( const string & in parm_id, int type )
void DeleteAllDesignVars()
string GetDesignVar( int index )
int GetDesignVarType( int index )
However, I actually suspect that you don't want to do that.
We've moved most batch mode commands from the command line prompt into
the scripting. The command line options were becoming increasingly
complex, and scripting can be so much more flexible.
To make life easy, we also made certain really commonly changed things
available through the command line.
So, if you want to read in a VSP file, or a DES file, you can pass
those on the command line -- and then run a particular script. That
way, if you are frequently changing your VSP or DES file, you don't
need to keep modifying your script to change a filename.
You probably want:
vsp baseline.vsp3 -des changes.des -script myscript.vspscript
Rob
> --
> You received this message because you are subscribed to the Google Groups
> "OpenVSP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
openvsp+u...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.