• 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. Restoring an object after dbDeleteObject

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 16804
  • 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

Restoring an object after dbDeleteObject

acook
acook over 11 years ago

Is it possible to save an object before I run dbDeleteObject so that it can be restored. I am working on a script where I may want to restore an instance I deleted.

Is the only way to do this brute force by saving all of the instances properties?

Example code:

inst = car( cvid->instances); Get my instance

backupInst = inst

dbDeleteObject(inst); delete inst

Both inst->?? and backupInst return:

     -> dbGetq: object is a purged/freed object - db:0x2057b31b

What I want to do next:

dbCreateObject(backupInst); A function that doesn't exist.....

  • Cancel
  • psill000
    psill000 over 11 years ago

    If you don't have a dbSave in your script, you should be able to do an undo and get the inst/objects back.

     

    If you are wanting specific inst/objects, you are going to have to write to a file or create a variable to hold the deleted inst/object value.  

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    The simple answer to the original question is "no". The closest is hiUndo, as the previous poster explained.

    There's no dbCreateObject - you have to use the specific dbCreate.* function to recreate the object. Bear in mind that deleting some objects actually can delete multiple objects - for example, if you delete a net, it will delete any terminals on that net, plus any pins on those terminals (not the figures though). I think it deletes the instTerms too. So restoring it will not be that straightforward.

    I'd really advise against any methodology which relied on deleting something temporarily and then restoring, unless that objects is quite constrained - i.e. it's a known type of object which you can capture the info about an recreate using the appropriate API, rather than trying to make this work for any arbitrary kind of object.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • acook
    acook over 11 years ago

    OK. Thank you for the responses. The item in question is specifically an instance within a schematic so I can do as you say and just save specific properties required to reproduce the item (brute force but it works alright).

    I'm curious, could you do something like create a temporary cellview and the set the cellView property of the instance you are "deleting" so that it moves to the temporary cellView?

    tempCvid = A new schematic

    inst = some schematic instance

    inst->cellView

    -> db.....the original schematic Cvid

    inst->cellView = tempCvid

    Message: *Error* unknown: (DB-370034): dbSetq: Cannot set attribute - cellView

    Doesn't look like this is possible.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 11 years ago

    Correct, you cannot change the cellView attribute.  Using dbCopyFig() you could copy the instance to the scratch cellview:

    scv = dbOpenCellViewByType("test" "scratch" "schematic" "schematic" "s")
    dbCopyFig(car(geGetSelectedSet()) scv)
    

    I've assumed that the instance in question is selected in the schematic, but if you are working non-graphically in that cellview too, you could use something like dbFindAnyInstByName() to get the instance database ID.

    Hope this helps.

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Or you could use dbMoveFig() instead to move it directly from one cellView to a scratch one, and then move it back again afterwards. That's even simpler.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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