Book a Demo

Author Topic: SysML flowport directions in conjugate ports  (Read 7489 times)

mike08

  • EA User
  • **
  • Posts: 20
  • Karma: +0/-0
    • View Profile
SysML flowport directions in conjugate ports
« on: June 17, 2015, 07:02:26 pm »
Using the conjugate property for a full port in SysML (EA12) does not show me the proper (reversed) flow directions of nested flowports. Rather the directions (the "<", ">", "<>" indications in the IDB) remain unchanged when I modify the conjugate property.
Tracing down the isConjugate Tag in the nested ports shows that they are unaffected by any modification to the container fullport.

Does anybody know how to enable/use the isConjugate Tag which would include the proper update to any nested port?

Best,
M.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: SysML flowport directions in conjugate ports
« Reply #1 on: June 17, 2015, 08:56:33 pm »
As said: this is long ago knowledge. But those times it was all manual work. Means that conjugate was local to each port and did not know about the other side.

q.

mike08

  • EA User
  • **
  • Posts: 20
  • Karma: +0/-0
    • View Profile
Re: SysML flowport directions in conjugate ports
« Reply #2 on: June 17, 2015, 10:41:46 pm »
I feared to read that - so if that did not change since then I'd better prepare for some scripting as a manual update would take me ages ...

Best,
M.

Architetto

  • Guest
Re: SysML flowport directions in conjugate ports
« Reply #3 on: March 01, 2018, 07:48:54 pm »
I'm running version 13 and EA still shows the wrong directions for conjugated ports. How do you guys handle this?

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +55/-3
    • View Profile
Re: SysML flowport directions in conjugate ports
« Reply #4 on: March 05, 2018, 08:45:55 am »
I'm running version 13 and EA still shows the wrong directions for conjugated ports. How do you guys handle this?

As far as I'm aware, it works. If it doesn't work for you, please submit a formal bug report. Thanks.
The Sparx Team
[email protected]