• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. IHM_CDT_CALLBACK

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 12952
  • 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

IHM_CDT_CALLBACK

Julien Terrier
Julien Terrier over 8 years ago

Hi,

In the CIW of my virtuoso environnement I added a menu toolbar with skill function, this menu allows to create some pcell. A callback procedure display an IHM then the users can put several fields to create their Pcell. 

In this IHM I would like add a CDT setting to avoid that the users put a wrong number. For instance In last IHM's field  the users mustn't put "0". My issue regards the way to implement a guard functions. In edit CDF the scope is only about library and cell (existing) and in my case the library or cell are not yed created. I don't know if I must create a callback linked with my IHM and how to do it, what is the relation with "Edit CDT" so on...

The method is not really clear for me I need some help and advice to make it.

Thank you.

  • Cancel
Parents
  • skillUser
    skillUser over 8 years ago
    Hi Julien,

    I'm not clear on your terminology but I will take some guesses: IHM => In House Menu? CDT => CDF (typo) and Edit CDT => Edit CDF
    However, even if my guesses are correct I don't really understand what you are trying to ask. If you are working with the Add Instance Cadence form then you would use CDF callbacks to put (upper and lower) bounds or limits on each parameter. If you are creating your own form and form fields then you would use the field callback to implement similar checking before attempting to create a parameterized instance. If I followed what you said you were hinting towards the latter because the instance doesn't exist yet, all you have is the parameter values and the instance has not been created yet. It would make sense to write 'central' or common checking functions that you could call from either a CDF callback or from the form field callback to implement the range checks.

    I'm not sure if this is helpful but your request wasn't quite clear.

    Best regards,

    Lawrence.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 8 years ago
    Hi Julien,

    I'm not clear on your terminology but I will take some guesses: IHM => In House Menu? CDT => CDF (typo) and Edit CDT => Edit CDF
    However, even if my guesses are correct I don't really understand what you are trying to ask. If you are working with the Add Instance Cadence form then you would use CDF callbacks to put (upper and lower) bounds or limits on each parameter. If you are creating your own form and form fields then you would use the field callback to implement similar checking before attempting to create a parameterized instance. If I followed what you said you were hinting towards the latter because the instance doesn't exist yet, all you have is the parameter values and the instance has not been created yet. It would make sense to write 'central' or common checking functions that you could call from either a CDF callback or from the form field callback to implement the range checks.

    I'm not sure if this is helpful but your request wasn't quite clear.

    Best regards,

    Lawrence.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information