• 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. Allegro X Scripting - TCL
  3. Update Title Block according to variant and using trigger...

Stats

  • State Verified Answer
  • Replies 4
  • Subscribers 13
  • Views 2530
  • Members are here 0
More Content

Update Title Block according to variant and using trigger function

Jim OMahony
Jim OMahony over 1 year ago

I have written a script to update title blocks in a design changing the part number value according to the current variant view.
At the moment, if the variant is changed the user must then select a custom menu item to update the part numbers in all of the title blocks.
I would like to automate this script with a trigger when the "View>Variant Mode..." selection is made. Does anyone know how to do this ?

The script is attached for anyone who wants to try it out or better still repost with improvements. This script uses a separate file in the design
directory to store the list of variant name and part number pairs. In pcb Skill it is possible to use a disembodied property list to store data in the
design. Is it possible to do this in Capture ?

Update_Variant_title_block.zip

  • Cancel
  • Sign in to reply
Parents
  • CadAP
    0 CadAP over 1 year ago

    HI jim OMahony,

    I have attached the zip file. I did some addition of the command to enable when user switch to variant mode.

    Please source the tcl script and switch in variant mode to see the changes.

    Also I have attached one sample code which will update Variant name property on title block as per current active Variant.

    Hope this will answer your query.

    Thanks

    https://community.cadence.com/cfs-file/__key/communityserver-discussions-components-files/138/Update_5F00_Variant_5F00_title_5F00_block.7z

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Jim OMahony
    0 Jim OMahony over 1 year ago in reply to CadAP

    Hi, thanks for the callback info. At the moment I am not getting any automatic change in the value of the property PN when I change the variant view.
    The RegisterAction command had a missing " which I corrected (in case anyone else looks at the file) but that has not made it work for me. I can manually run the script after each change to the variant view and that still works correctly.
    I am using Orcad Capture CIS and I am wondering if that would make a difference. I have also tried _cdnOrPostVariantViewMode just in case but with no avail.
    I will have to look at the sample code at a later date to see if I can get that to work.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Jim OMahony
    0 Jim OMahony over 1 year ago in reply to CadAP

    Hi, thanks for the callback info. At the moment I am not getting any automatic change in the value of the property PN when I change the variant view.
    The RegisterAction command had a missing " which I corrected (in case anyone else looks at the file) but that has not made it work for me. I can manually run the script after each change to the variant view and that still works correctly.
    I am using Orcad Capture CIS and I am wondering if that would make a difference. I have also tried _cdnOrPostVariantViewMode just in case but with no avail.
    I will have to look at the sample code at a later date to see if I can get that to work.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
  • ggeorgg
    ggeorgg over 1 year ago in reply to Jim OMahony
    This reply was deleted.
    • Cancel
    • Cancel
  • Jim OMahony
    0 Jim OMahony over 1 year ago in reply to ggeorgg

    Thanks ggeorgg, the file is excellent. Just what I need to tidy up my code.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
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.

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

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