• 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. MiniStatus Forms

Stats

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

MiniStatus Forms

archive
archive over 19 years ago

I am developing utilities using MiniStatus forms. I have to retart Allegro, every time I make a change to the form, to see those changes. Is anybody aware of a way around this?

Cheers, Dave


Originally posted in cdnusers.org by Dave Elder
  • Sign in to reply
  • Cancel
  • archive
    archive over 19 years ago

    For development, I change the form file name after every change.

    file1.form
    file2.form
    file3.form
    .
    .
    .

    Once all is good, I rename to what it should be and restart Allegro.

    If you need to test the layout (no functionality)of forms that you are creating dynamically, I suggest using the axlFormTest procedure to test the forms.


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

    Good work around, thanks!


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

    Dave,

    Another method that would work would be to get the date/time and use that to construct the filename. That would insure uniqueness. Once you get what you need, delete all but the most recent form.

    OR

    Create a global variable when you launch Allegro and everytime you reload the .il file, have it automatically increment the variable. Then use the variable to construct the form filename.

    Just a couple of other ideas.


    Originally posted in cdnusers.org by cdavies
    • 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