• 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. PCB Design
  3. Creating .PDF using Tcl/Tk Utilities in Capture 16.3

Stats

  • Locked Locked
  • Replies 22
  • Subscribers 170
  • Views 18725
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Creating .PDF using Tcl/Tk Utilities in Capture 16.3

Goblin60
Goblin60 over 14 years ago

 All,

Here's somthing a little different. I'd like to export a .pdf using the application found in  Accesories--->Cadence Tcl/Tk utilites. This gizmo (when working) produces a searchable pdf which allows one to click on components within the pdf and see properties. I've seen this work in older versions of software. Here's the hitch; I need the postscript driver path for the .pdf editor Bluebeam. I can also use the postscript friver path for Adobe Acrobat Distiller but I prefer to use Bluebeam. Attached is a .png that shows you what I am refering to. Any info will be appreciated.

Cheers,

Ron Scott

  • pdf_question.png
  • View
  • Hide
  • Cancel
Parents
  • hobbss
    hobbss over 14 years ago

     That's what is so confusing --> I couldn't find the error message in the code either.

     I have already tried adding the the path to gswin32c.exe to the PATH environment variable -- no change (still doesn't work).

     I haven't actually configured a "Printe to File" Postcript printer.  All I did was install ghostscript, and then point Capture to gswin32c.exe.  This worked originally with no issues (I didn't even need to change the PATH environment variable).  Because nothing changed in Capture, and because I can't find the error text in the script, I think it must be some kind of system error.  I just don't know what...

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • hobbss
    hobbss over 14 years ago

     That's what is so confusing --> I couldn't find the error message in the code either.

     I have already tried adding the the path to gswin32c.exe to the PATH environment variable -- no change (still doesn't work).

     I haven't actually configured a "Printe to File" Postcript printer.  All I did was install ghostscript, and then point Capture to gswin32c.exe.  This worked originally with no issues (I didn't even need to change the PATH environment variable).  Because nothing changed in Capture, and because I can't find the error text in the script, I think it must be some kind of system error.  I just don't know what...

    • Cancel
    • Vote Up 0 Vote Down
    • 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