Opened 8 years ago

Closed 19 months ago

#4551 closed defect (fixed)

Do not allow connection of different connector types

Reported by: Christian Kral <dr.christian.kral@…> Owned by: Adrian Pop
Priority: high Milestone: 1.21.0
Component: OMEdit Version:
Keywords: Cc: Adrian Pop, Martin Sjölund

Description

In the actual version of OMEdit it is possible to, e.g., connect a rotational to an electrical connector or connect a signal connector to a thermal connector. This does not make sense and shall not be allowed.

Attachments (1)

Connections.png (7.5 KB ) - added by Christian Kral <dr.christian.kral@…> 8 years ago.
Image showing connections not be allowed

Download all attachments as: .zip

Change History (18)

by Christian Kral <dr.christian.kral@…>, 8 years ago

Attachment: Connections.png added

Image showing connections not be allowed

comment:1 by massimo ceraolo, 8 years ago

It is even possible to connect to a connector that should not be visible. for instance connecting an electric connector to the thermal connector of a resistor for which useHeatPort=false

comment:2 by Adeel Asghar, 8 years ago

Cc: Adrian Pop Martin Sjölund added

AFAIR we use to have this check but then dropped for #2450.
We need to instantiate the model which leads to other issues as well so we simply allow the user to make connections and then show the errors the model is simulated.

Maybe Adrian or Martin has some better ideas.

in reply to:  2 comment:3 by massimo ceraolo, 8 years ago

AFAIR we use to have this check but then dropped for #2450.

If, with a reasonable programming effort, it is possible to forbid unacceptable connections, in my opinion this should be pursued.

It would help students and beginners to avoid trivial mistakes, and help us teachers to promote OM better.

In case you decide to allow optionally incorrect connections, for me this option should not be the default.

comment:4 by dr.christian.kral@…, 8 years ago

I agree, that students often run into problems by connecting the wrong components. It were therefore very helpful in education to not allow connection between non-matching connectors.

comment:5 by Adeel Asghar, 7 years ago

Milestone: Future1.12.0
Resolution: duplicate
Status: newclosed

See #4337.

comment:6 by massimo ceraolo, 7 years ago

I don't think that this is duplicate of 4337.
May I ask you to reopen this? Just to keep trace of the discussion here and of the difference between this and #4337.

comment:7 by Adeel Asghar, 7 years ago

I don't see a difference between the two.
A connection of different connector types is indeed an invalid connection, right?

Version 0, edited 7 years ago by Adeel Asghar (next)

comment:8 by Francesco Casella, 7 years ago

I guess what @ceraolo meant was that the discussion in this ticket is also relevant. I've added a reference to this ticket to #4337

comment:9 by massimo ceraolo, 7 years ago

Adeel,
Sorry for awfully tampering with your comment. I didn't realise that I was modifying it!

Last edited 7 years ago by massimo ceraolo (previous) (diff)

comment:10 by Adeel Asghar, 7 years ago

Milestone: 1.12.01.13.0
Resolution: duplicate
Status: closedreopened

@ceraolo I do agree with you that the description on the both tickets are different buy maybe at the compiler level just a single fix is needed to close both tickets.

I am reopening this ticket so we don't miss out the valuable discussion done here.

comment:11 by Adeel Asghar, 7 years ago

Owner: changed from Adeel Asghar to Adrian Pop
Status: reopenedassigned

comment:12 by Francesco Casella, 6 years ago

Milestone: 1.13.01.14.0

Rescheduled to 1.14.0 after 1.13.0 releasee

comment:13 by Francesco Casella, 5 years ago

Milestone: 1.14.01.16.0

Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0

comment:14 by Francesco Casella, 4 years ago

Milestone: 1.16.01.17.0

Retargeted to 1.17.0 after 1.16.0 release

comment:15 by Francesco Casella, 4 years ago

Milestone: 1.17.01.18.0

Retargeted to 1.18.0 because of 1.17.0 timed release.

comment:16 by Francesco Casella, 4 years ago

Milestone: 1.18.0

Ticket retargeted after milestone closed

comment:17 by Adeel Asghar, 19 months ago

Milestone: 1.21.0
Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.