Stats

  • Locked Locked
  • Replies 7
  • Subscribers 143
  • Views 14943
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Changing top view reference in a config view

skillprogramme

I can't find any way to change the top view of a config view corresponding to an ADEXL view. It is possible to retrieve the top view by fex

hdbGetTopCell(hdbConfig)

hdbGetTopView(hdbConfig)

hdbGetTopLib(hdbConfig) 

but there's no obvious way to set it (hdbSetTopCell fex). The hdbBind doesn't seem to provide the functionality and the example documentation in your_install_dir/tools/hdb/examples/hdbTraverse.il doesn't either. The config file is not a big thing, so it is easy to hack a solution, but it would better to do it through an API. Any help is very appreciated, I am (still) a relatively inexperienced SKILL programmer.

Max 

Parents
  • Andrew Beckett

    Max,

    I agree. I have a CCR to do a thorough review of the ADE XL documentation, and also the private/public status of many of the functions. The HDB is not in quite such bad shape, but there are still a few holes.

    In general, when functions are made public, the documentation follows shortly. So there's no list of public functions separate from what is documented - the rules are that if it's public, it should be documented (there are a few allowed exceptions, usually for something that has been end-of-lifed, say, but these are rare).

    In this case, axlGetCornerName and axlSetCornerName are private. However, they break our naming rules too - it was all a matter of available resources at the right time. The best thing to do is to log a service request and ask for these to be made public and documented - it's far better for this to come directly from a named customer, and not just me ;-)

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Max,

    I agree. I have a CCR to do a thorough review of the ADE XL documentation, and also the private/public status of many of the functions. The HDB is not in quite such bad shape, but there are still a few holes.

    In general, when functions are made public, the documentation follows shortly. So there's no list of public functions separate from what is documented - the rules are that if it's public, it should be documented (there are a few allowed exceptions, usually for something that has been end-of-lifed, say, but these are rare).

    In this case, axlGetCornerName and axlSetCornerName are private. However, they break our naming rules too - it was all a matter of available resources at the right time. The best thing to do is to log a service request and ask for these to be made public and documented - it's far better for this to come directly from a named customer, and not just me ;-)

    Regards,

    Andrew.

Children
No Data

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.