It is more more efficient in both performancce and memory to use a
rectangle in the database then a shape.
If you want the additional overhead of forcing a shape then
use the axlDBCreateOpenShape/axlDBCreateCloseShape APIs and pass a t as
the second
argument to axlDBCreateCloseShape.
Note axlDBCreateShape is implemented as
axlDBCreateCloseShape( axlDBCreateOpenShape( r_path fill layer
netName parent))
so to force a shape do a
axlDBCreateCloseShape( axlDBCreateOpenShape( r_path fill layer
netName parent) t)
Anyone knows how to fix this? Or might this be a bug?
I confirm this behavior under 15.2 .
Methinks SKILL is trying to "help" you by up-classifying your shape if it fits one of Allegro's predefined shapes.
One workaround would be to "clip the corners" off your shape so SKILL would no longer see it as a true rectangle. But now you'd need to craft a function to calculate where to clip each corner based on the overall scale of the shape. Not difficult but should not be necessary in the first place.
Fortunately, within SKILL itself this RECTANGLE object has an objType of "shape" so all your code will process it just fine.
HTH,
Chris Walters local Cadence guru (Apple)
To view the archives of this list please login at //www.freelists.org. Our list name is icu-pcb-forum or go to //www.freelists.org/archives/icu-pcb-forum/
Problems or Questions: Send an email to icu-pcb-forum-admins@xxxxxxxxxxxxx
SUBSCRIBE: icu-jobs-forum-subscribe@xxxxxxxxxx POST: icu-jobs-forum@xxxxxxxxxx -----------------------------------------------------------