<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.cadence.com/Community/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Using Constraints to Pass Configuration Options in the Unit Hierarchy (Top-Down approach)</title><link>http://www.cadence.com/Community/blogs/fv/archive/2009/06/26/using-constraints-to-pass-configuration-options-in-the-unit-hierarchy-top-down-approach.aspx</link><description>To allow for increased solvability, some constraints that were previously uni-directional with the old &amp;ldquo;Pgen&amp;rdquo; generator are now treated by IntelliGen in a bi-directional manner by default. This behavior dramatically improves solvability and</description><dc:language>en</dc:language><generator>CommunityServer 2007.1 (Build: 20917.1142)</generator></channel></rss>