• 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. axlForm/axlMeter display during process

Stats

  • Replies 7
  • Subscribers 158
  • Views 3555
  • Members are here 0
More Content

axlForm/axlMeter display during process

archive
archive over 17 years ago

Hello All.

I have a form with fixed texts and texts that are updated during the process.
During the process, only updated texts are displayed, fixed ones are only displayed at the en of the process.
Is there a way to fix this problem?

Thanks.


Originally posted in cdnusers.org by willbi
  • Sign in to reply
  • Cancel
Parents
  • archive
    archive over 17 years ago


    I tried to add a progress bar to this form:
    The form is written on the disk.
    It is loaded with:
    fabForm=axlFormCreate( (gensym) "./fabForm.form" '(e outer) 'fabForm_Action t)

    Then it is displayed.

    I defined a "bar" PROGRESS field:
    fprintf(fabForm "FIELD bar\n")
    fprintf(fabForm "FLOC 5 19\n")
    fprintf(fabForm "PROGRESS 50 4\n")
    fprintf(fabForm "ENDFIELD\n"
    I define a list:
    barList=list(1 length(l_comps) 0)
    axlFormSetField(fabForm "bar" barList )
    then I update it with for each compdef:
    barList=list(1 length(l_compdefs) cdnum)
    axlFormSetField(fabForm "bar" barList )
    Then the progress bar works inside the form. But with always the display problem. Updated texts and the bar are displayed.

    I tried with an axlMeter.
    I can't succeed to put the axlMeter inside the form, but if it runs outside the form, the form is totally and fully displayed (all texts, text borders...)
    I saw that axlMeter can update a progress in a form if this progress is named "bar". But the axlMeterCreate("", "", nil, "fabForm") creates a new form and update only the bar.I got two forms, one with updated texts and another one with the bar!!...
    If the axlMeter is opened outside then I get everything but 2 progress bars.
    And if I create the Meter and Destroy it, the form is well displayed but some texts are truncated....


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


    I tried to add a progress bar to this form:
    The form is written on the disk.
    It is loaded with:
    fabForm=axlFormCreate( (gensym) "./fabForm.form" '(e outer) 'fabForm_Action t)

    Then it is displayed.

    I defined a "bar" PROGRESS field:
    fprintf(fabForm "FIELD bar\n")
    fprintf(fabForm "FLOC 5 19\n")
    fprintf(fabForm "PROGRESS 50 4\n")
    fprintf(fabForm "ENDFIELD\n"
    I define a list:
    barList=list(1 length(l_comps) 0)
    axlFormSetField(fabForm "bar" barList )
    then I update it with for each compdef:
    barList=list(1 length(l_compdefs) cdnum)
    axlFormSetField(fabForm "bar" barList )
    Then the progress bar works inside the form. But with always the display problem. Updated texts and the bar are displayed.

    I tried with an axlMeter.
    I can't succeed to put the axlMeter inside the form, but if it runs outside the form, the form is totally and fully displayed (all texts, text borders...)
    I saw that axlMeter can update a progress in a form if this progress is named "bar". But the axlMeterCreate("", "", nil, "fabForm") creates a new form and update only the bar.I got two forms, one with updated texts and another one with the bar!!...
    If the axlMeter is opened outside then I get everything but 2 progress bars.
    And if I create the Meter and Destroy it, the form is well displayed but some texts are truncated....


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