• 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. LibManager Edit Trigger/Callback

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 144
  • Views 6079
  • 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

LibManager Edit Trigger/Callback

dfick
dfick over 11 years ago

 Hi,

 In the Virtuoso Library Manager when a cellview is double-clicked, it automatically opens for edit. However, I would like some things to happen just before a cell view is opened for edit (make a backup copy, change file permissions, etc). Is there a way to set an event trigger or callback that occurs when a cellview is opened for edit? The only commands that I could find with similar functionary are "ccpPostExpandTrigger", which is trigger for copying files, and "cdsLibManager.main dblClickEditCellView", which is a flag enabling/disabling the double-click-to-edit functionality.

 Thanks

 Edit: I am using ic-6.1.5.500.16

  • Cancel
Parents
  • dfick
    dfick over 11 years ago

     Thanks, I distilled your example down to a smaller case that does what I need. Before auto-checkout it checks the views to see if they need to be set to editable, so on read it wont do anything, on write-but-already-editable it wont do anything, but on write-but-not-editable it is ready to do something.


    procedure(triggerPing(@optional objList isBatch)

           foreach(mapcar obj objList
                if(obj->type != 'ddViewType
                      then
                            t ; only check for view types
                      else
                            access_modes = ddGetObjAccess(obj "o")
                            rexCompile("w")
                            is_writable = rexExecute(access_modes)

                            if(is_writable
                                then
                                     printf("View is already editable\n")
                                     t ; don't need to do anything
                                else
                                     printf("Need to set edit mode\n")
                                     printf("PING\n");
                                     t
                            )
                 )
           )


    ddRegTrigger("PreAutoCheckOut" `triggerPing)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • dfick
    dfick over 11 years ago

     Thanks, I distilled your example down to a smaller case that does what I need. Before auto-checkout it checks the views to see if they need to be set to editable, so on read it wont do anything, on write-but-already-editable it wont do anything, but on write-but-not-editable it is ready to do something.


    procedure(triggerPing(@optional objList isBatch)

           foreach(mapcar obj objList
                if(obj->type != 'ddViewType
                      then
                            t ; only check for view types
                      else
                            access_modes = ddGetObjAccess(obj "o")
                            rexCompile("w")
                            is_writable = rexExecute(access_modes)

                            if(is_writable
                                then
                                     printf("View is already editable\n")
                                     t ; don't need to do anything
                                else
                                     printf("Need to set edit mode\n")
                                     printf("PING\n");
                                     t
                            )
                 )
           )


    ddRegTrigger("PreAutoCheckOut" `triggerPing)

    • 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