Stats

  • Locked Locked
  • Replies 1
  • Subscribers 144
  • Views 12675
  • Members are here 0
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

schematics addTitleBlock and LayoutXL : triggering question

samung

Hello,

I have an issue with the titleblock generation in schematics and layoutXL.

The issue is the folowing :

The titleblock is generated in layout (this not wished at all) in the case:

1-Open schematic via library manager. The corresponding layout must be closed.

2-In this schematic , menu Launch > Layout XL. The titleblock is generated in layout just opened.

In my automatic titleblock generation script, I have a "deRegUserTriggers" line :

deRegUserTriggers(

t_viewType

[ s_appTrigger [ s_menuTrigger [ s_postInstallTrigger ] ] ]

)

such as :

deRegUserTriggers("schematic" nil nil 'CCSaddSchTitleCell)

My understanding of the issue is that the "t_viewType" for a layout view can be in some specific conditions "schematic" ?!!

Would you have a way to avoid triggering the execution of the CCSaddSchTitleCell procedure when the layoutXL is launched ?

Thanks a lot !!

P.

  • The viewType determines how the tools address the data. When the viewType is schematic, it is expected to be instances, notes and connectivity, the logical view. When the viewType is maskLayout, it should contain physical data. If you have layout data in a schematic viewType (the view name can be anything), the tools will treat it like a schematic and you may not be able to execute layout tools. Layout XL should never open a view named "layout" as a schematic viewType, if it is, there is something wrong with your setup.

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.