• 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. How to keep your variables in the design?

Stats

  • Replies 25
  • Subscribers 160
  • Views 12716
  • Members are here 0
More Content

How to keep your variables in the design?

Silver John
Silver John over 14 years ago

Hi, All.

I have a script that creates a form with several fields. I want to save the contents of these fields in design, and the next time when I open the design and launches the script I have already configured the form.

There are functions for including the file or string to .brd-file, there are functions for working with the properties of the design...

What is the best way to save my settings?

Maybe someone has an example code?

Thank you.

  • Sign in to reply
  • Cancel
Parents
  • fxffxf
    fxffxf over 14 years ago

    The basic issue with application attachments without password protection is that they rely on the good behavior of other Skill programmers. No password protection assumes that no other Skill programmer will muck with your attachment since they didn't create it.If you are  developing and using Skill programs within one company this may be a good assumption.

    For example, you can write some Skill code to replace the TIF Quickview attachment with some other data and see what happens when Allegro attempts to use this attachment. If Quickview application code password protected this attachment then it knows the data is valid since only it can modify the attachment.

    You must remember that attachments are a storage mechanism for user data. A Skill program is usually interacting with the user through some UI like a form to present this stored data. Storing the attachment password protected and encyrpting skill is code doesn't prevent this use model it just adds a level of security.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • fxffxf
    fxffxf over 14 years ago

    The basic issue with application attachments without password protection is that they rely on the good behavior of other Skill programmers. No password protection assumes that no other Skill programmer will muck with your attachment since they didn't create it.If you are  developing and using Skill programs within one company this may be a good assumption.

    For example, you can write some Skill code to replace the TIF Quickview attachment with some other data and see what happens when Allegro attempts to use this attachment. If Quickview application code password protected this attachment then it knows the data is valid since only it can modify the attachment.

    You must remember that attachments are a storage mechanism for user data. A Skill program is usually interacting with the user through some UI like a form to present this stored data. Storing the attachment password protected and encyrpting skill is code doesn't prevent this use model it just adds a level of security.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
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