Years ago when we held Mentor to the flame for automation; I never dreamed we would have to be using it to fix major defects and functionality. Keep up the good work, and now Ill go audit some of my latest translations.
This kind of stuff scares me.
Thanks for posting this and logging a defect. Engineering are currently reviewing the defect and test case to come up with a solution. This is the first time that we have encountered the use of 'Unknown' type in DC for components that go to layout. You can be assured this is being given our fullest attantion.
Based on the critical scope of the issue, I wanted to share with other users
who might be on the same path of migrating to DxD.
I understand you can't test for every combination possible at times, but its
good to see that you agree with the "potential" issue that have significant consequences.
Thanks again & we are looking forward to DxD and the VX releases.
I would also suggest review of this item during your potential update .
It is also relevant to your developers and incorrect state changes,
DC Symbols with Symbol type of edge connector are incorrectly translating to “PIN” vs “MODULE”
this is making placement of any symbol (if more than 1 pin) invalid
This wouldn't be a Composite, that represents a hierarchical block. It would/should be module.