Stats

  • Replies 17
  • Subscribers 164
  • Views 23803
  • Members are here 0
More Content

Change text block size, Allegro script and skill

skillnewbie

hi,

I want to change a text block size (#16). i run a script recording and get this from the *.scr 

 setwindow pcb
trapsize 302
define text
setwindow form.textblock
FORM textblock 16 width 0.1000
FORM textblock 16 height 0.1000
FORM textblock 16 line_spacing 0.0200
FORM textblock 16 photoplot_width 0.0100
FORM textblock done 
setwindow pcb

just wonder what the FORM means in a script file...it is not a valid command in Allegro

 is it possible to enclose the FORM statements in skill code?

Parents

  • Hi Sam,

    Stop the script by using the menu: file ->script ->stop.

    Of course, resetting the text blocks in your library won't help unless those text blocks match your designs. The best method is to reserve and standardise the first 16 (minimum) text blocks across your company. The Cadence defaults might be OK. We use blocks 1, 2 and 3 (customised) for library reference designators (depending on the size of the part) and 17 for silkscreen text.

    I have some Skill that might help do what you want. However, running utilities across an entire library isn't for the faint hearted. If you have parts created in older versions of Allegro you will have to run dbdoctor on those parts before you start- easy if they are in one folder - not so easy otherwise. You should take a backup copy of each library before updating it.

    Good luck, Dave

Reply

  • Hi Sam,

    Stop the script by using the menu: file ->script ->stop.

    Of course, resetting the text blocks in your library won't help unless those text blocks match your designs. The best method is to reserve and standardise the first 16 (minimum) text blocks across your company. The Cadence defaults might be OK. We use blocks 1, 2 and 3 (customised) for library reference designators (depending on the size of the part) and 17 for silkscreen text.

    I have some Skill that might help do what you want. However, running utilities across an entire library isn't for the faint hearted. If you have parts created in older versions of Allegro you will have to run dbdoctor on those parts before you start- easy if they are in one folder - not so easy otherwise. You should take a backup copy of each library before updating it.

    Good luck, Dave

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.