• 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. Custom HTML reports in 17.2

Stats

  • Replies 6
  • Subscribers 160
  • Views 17302
  • Members are here 0
More Content

Custom HTML reports in 17.2

EvanShultz
EvanShultz over 7 years ago

I have written some nice reports for internal use, both text reports and HTML reports. Both displayed fine in 16.6.

In 17.2, my text reports are still OK but the HTML reports just display the raw HTML text instead of being formatted and displaying as an HTML page. The Allegro SKILL 17.2 manual, page 1272, still mentions both types of reports being available. The included Allegro reports that are HTML format still work OK, so it’s something about my custom HTML reports.

I looked on COS and the PCB Design forum and didn’t see anything. Neither does $CDSROOT\share\pcb\examples\skill have anything about this that I can find. Then I searched for “html” in User Prefs and found a couple variables. Unchecking “allegro_html_qt” makes the reports display properly. Now knowing this, I found a few entries on COS that sounds like the HTML viewer has changed in 17.2 from OpenGL to Qt. Perhaps that’s the issue?

Has anybody else run into this issue? What fixes it? Or alternatively, if you have a custom HTML report working in 17.2 with the allegro_html_qt variable checked, how is your report formatted?

Here is the displayed text from an example board I made with allegro_html_qt checked. This is exactly what is displayed in the report window; Allegro does not understand this is HTML and should be displayed as such:

<html><b><u>Design name</u>&nbsp; C:/DATA/Projects/Cadence/test/comp_lead_prep/worklib/comp_lead_prep/physical/comp_lead_prep166.brd<br><u>Date</u>&nbsp; Mon Mar 12 16:11:00 2018</b><br><br><table border="1"><caption><b><u>QSC Component Lead Prep Report</u></b></caption><tr><th>Ref Des</th><th>Part Number</th><th>Footprint Name</th><th>Tooling</th><th>Lead Prep Doc</th></tr><tr><td>Q1</td><td>QD-000373-00</td><td>Q_MFN_TO220FLUP150</td><td>B3</td><td>RD-000487-00</td></tr><tr><td>Q3</td><td>QD-000284-00</td><td>Q_MFN_TO247FLUP220</td><td>C</td><td>RD-000488-00</td></tr><tr><td>Q4</td><td>QD-000284-00</td><td>Q_MFN_TO247PRPC</td><td>ND1</td><td>RD-000042-00</td></tr></html>
  • Sign in to reply
  • Cancel
  • HJerry
    HJerry over 3 years ago in reply to EvanShultz

    Hi Evan,

    Thanks for this update, I know it is 8 months old but I just ran into this issue.

    I still am having an issue with table borders. They do not show up. Did you run into this issue?

    Thanks,

    Jerry

    • 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