• 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 PCB Editor
  3. Running programs killed by Undo and Update symbols

Stats

  • Replies 3
  • Subscribers 158
  • Views 13166
  • Members are here 0
More Content

Running programs killed by Undo and Update symbols

archive
archive over 18 years ago

I wondered if anybody else has this problem.
It happens when the program is running (the form is displayed), and I use Undo or Update symbols.
 
Its usually a minor annoyance, except for one program that modifies color and visibility settings. When the program exits normally, the color and visibility settings are restored, but if the program stops abnormally, then they aren't restored.

Does anybody know if this is a fixable problem, or can I put something in the code to detect this and exit gracefully?

Thanks!

- Geoff


Originally posted in cdnusers.org by Geoffm
  • Sign in to reply
  • Cancel
  • archive
    archive over 18 years ago


    Wrap the code throwing the error with the errset function. See the Error Handling section in the Skill User Guide.

    If an error is thrown then errset.errset will be non-nil


    Originally posted in cdnusers.org by fxf
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • archive
    archive over 18 years ago

    Thanks fxf

    Its going to take me awhile to check the errset function out. I have never used it before in Skill. I have used error trapping in Visual Basic, and it seems like it would be similar to Skill.

    Its hard to know where to start because, the program form is displayed but the program is not actively doing anything. So where would I put the errset function?

    Anyways I need to get my head into it.


    Originally posted in cdnusers.org by Geoffm
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • archive
    archive over 18 years ago


    If you create a function that calls makes several axl and Skill calls I would place the errset around that function.
    Placing it around individual axl or Skill APIs would not be a good programming style.

    Basically, it should be placed around a set of related programming like updating the database.


    Originally posted in cdnusers.org by fxf
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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