Stats

  • State Not Answered
  • Replies 3
  • Subscribers 13
  • Views 6331
  • Members are here 0
More Content

Orcad Capture TCL scripting documentation

Diego cmre

Talking about TCL scripting, in a chapter of Cadence help documentation, under  "OrCAD Capture Information Model" / "Basic Object"  there are many reference to header file like as: DboBase.h DbProp.h DboValue.h Value.h DboUProp.h .......

but I'm not able to find these file, probably they contains the enumerators used for many properties fields,

I'm trying to read via a tcl script EffectivePropsIter, the field PropType refers to "Value.h" file !

In documentation you can read the following:

Example Use of EffectivePropsIter

The EffectivePropsIter is somewhat more complex than normal iterators since it does not return an object. Since it is not possible to query the object about itself, extra information is returned by the NextEffectiveProp() function:

PropName: string which is name of property
PropValue: string which is value of property in string form
PropType: Value type return - see Value.h for enumeration
bEditable: TRUE if the property can be edited, else FALSE

Does anyone know the location of these files?

Parents
  • RT202503126350
    0

    bump. 

    How can one find information about this kind of stuff?  Is the only solution to just post a query on the forums, and hope a Cadence developer can answer?

    As a budding Capture TCL coder, the reference bible: the pdf "OrCAD Capture Tcl/Tk Extensions – Application Notes", has lots of great information, but leaves a lot unexplained and undocumented, especially compared to other languages. 

    What are the values/constant names for a given enumerated type?( ColorT, LinestyleT, ObjectTypeT etc). 

    Explanations of arguments for a given command/function (what happens when a given boolean is set to true or false)?  

    In the referenced pdf, in section 3.2.1.1 (page 25), it explains how to use "info commands" to find command names, and then how to call the command name without argument parameters i.e. "DboLib_GetName" and then use the response " Wrong number of arguments: DboLib_GetName self name argument 1" to see which arguments the command expects.  But for overloaded functions, where it can be called with more or fewer commands, it just spits out, for example, "No matching function for overloaded 'DboPage_ReplaceInst'", so no information can be gleaned.

    The original poster references this "OrCAD X Capture Information Model" documentation, which seems to explain a lot about objects in the Capture database model, but doesn't appear to relate directly to TCL.  It references a bunch of header files (DboValue.h Value.h DboUProp.h .......).  Are these available in the install directory or elsewhere?  Why is the documentation provided, but the referenced files are nowhere to be found.

    I apologize for this being more of a rant than a specific question, but I feel like I must be missing something.  I should be able to look this stuff up somewhere.

  • PatEscher
    0 in reply to RT202503126350

    as far as I recall, many, many, many years back there was a c or c++ API available for Capture, probably not officially released to customers. I suspect that the docs still refer partially to it.

    And I fully agree with your comments. the pdf is not really a API documentation. it is a list of available functions (not even complete) without any good description. Furthermore, I have not seen any updates to this document since many years.

Reply
  • PatEscher
    0 in reply to RT202503126350

    as far as I recall, many, many, many years back there was a c or c++ API available for Capture, probably not officially released to customers. I suspect that the docs still refer partially to it.

    And I fully agree with your comments. the pdf is not really a API documentation. it is a list of available functions (not even complete) without any good description. Furthermore, I have not seen any updates to this document since many years.

Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.