You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ah Ok I see I was not defining ComponentPin from a PadstackInstance.name. The documentation should explain this. The API allows creating ComponentPin from a randon string.
Thanks
@svandenb-dev I believe this is the same way component pins are created/added to a component in the .NET API? I'm open to the idea of maybe automatically handling the step of creating the ComponentPin object, but do you think it would be better for that to be handled in the pyedb API since that is a high level wrapper around the pyedb-core API? Thanks!
@drewm102 I think this would need to be handled at the wrapping layer like you said. Adding the Components Pins is done at the definition level, so to my understanding ComponentPin should be create when we create the ComponentDefinition then we place pin "1", "2".... When we add the member the PadstackInstance will have to be renamed with the existing ComponentPin name. The code shown by @chenchienjacklin will assign the PadstackInstance name to all component sharing the same defintion, do you agree ?
🔍 Before submitting the issue
🐞 Description of the bug
I am creating a component
new_cmp = GrpcComponentGroup.create(self._active_layout, component_name, compdef.name)
I got the padstackinstance
Did I missed something ?
📝 Steps to reproduce
NA
💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
No response
🐍 Which Python version are you using?
3.11
📦 Installed packages
The text was updated successfully, but these errors were encountered: