Stats

  • Locked Locked
  • Replies 2
  • Subscribers 167
  • Views 14830
  • 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

Custom Layer Views Changed from 16.6?

JERATSSI

In 16.6 I had a bunch of custom views defined under scripts that I could jump through, bottom view, topview, inner1view, etc.  The change to 17.2 broke all these scripts and it appears the menus have changed internally

16.6:

"cvf layer_tree_item 'Stack-Up'
cvf layers_visible stack-up stack-up/top TRUE
cvf layers_visible stack-up stack-up/soldermask_top TRUE
cvf layers_visible stack-up stack-up/pastemask_top TRUE
cvf layers_visible stack-up stack-up/through_all TRUE
cvf layers_visible stack-up stack-up/package_top TRUE"

17.2:

"QtSignal CVDLayerContainer CVDVisibilityOff clicked
QtSignal CVDLayerTable VertHeader clickedCheckBox 0
QtSignal CVDLayerSplitter CVDLayerTable dataChanged Top Pin
QtSignal CVDLayerTable VertHeader clickedCheckBox 4
QtSignal CVDLayerSplitter CVDLayerTable dataChanged Soldermask_Top Pin
QtSignal CVDLayerTable VertHeader clickedCheckBox 6
QtSignal CVDLayerSplitter CVDLayerTable dataChanged Pastemask_Top Pin
QtSignal CVDLayerTable VertHeader clickedCheckBox 8
QtSignal CVDLayerSplitter CVDLayerTable dataChanged Filmmasktop Pin
QtSignal CVDLayerTable VertHeader clickedCheckBox 10"

Besides not having an easily human repeatable format if I end up having extra layers added the checkbox number moves.  For example, if one design has a MECH layer added to PkgGeo and another has MECH1 and MECH2, that means the scripts will not work the same.  I ran into this on a design where for some reason the placebound bottom was erroneously showing in my topview in one design but not the other. Also one designer took my hotkeys and scripts and he didn't have any inner layers defined and when calling anything that modified etch the editor would crash immediately without a warning.

Is there a better way to view scripts that can transfer through designs?

Parents

  • From a bunch more research I found a different way than replay scripts to switch through layer views.  I create colorviews and recall them via hotkey.  If anyone else stumbles upon this and doesn't know what this means as I didn't, here's an explanation:

    Through your favorite view menu turn on and off all layers you want.

    Type "colorview create" to save this view, I always do Replacement Complete and uncheck preserve zoom and flip, choose where to save and hit save

    You can reload colorviews either by typing "colorview load" to bring up a dialog box to find the view, or from the dropdown on the visibility window

    Here's an example of how to load via hotkey if you place this in your env file, be aware you might have to add the views folder in share->pcb->text->views to your paths in user prefs

    funckey ~E 'settoggle viewvar topview bottomview bothview inner1view inner2view; colorview load $viewvar; echo view = $viewvar'

Reply

  • From a bunch more research I found a different way than replay scripts to switch through layer views.  I create colorviews and recall them via hotkey.  If anyone else stumbles upon this and doesn't know what this means as I didn't, here's an explanation:

    Through your favorite view menu turn on and off all layers you want.

    Type "colorview create" to save this view, I always do Replacement Complete and uncheck preserve zoom and flip, choose where to save and hit save

    You can reload colorviews either by typing "colorview load" to bring up a dialog box to find the view, or from the dropdown on the visibility window

    Here's an example of how to load via hotkey if you place this in your env file, be aware you might have to add the views folder in share->pcb->text->views to your paths in user prefs

    funckey ~E 'settoggle viewvar topview bottomview bothview inner1view inner2view; colorview load $viewvar; echo view = $viewvar'

Children
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.