Opened 11 years ago

Closed 7 years ago

#2379 closed defect (invalid)

Expandable connectors with expandable connector components fails with connect

Reported by: petar Owned by: adrpo
Priority: critical Milestone: Future
Component: Frontend Version: trunk
Keywords: Cc:

Description

This example illustrates the problem:

package ExpandableTest
expandable connector A
  B b;
end A;
expandable connector B
end B;

model Test
   A a1,a2;
equation
  connect(a1.b.new,a2.b.new);
end Test;
end ExpandableTest;

This is critical for the VehicleInterfaces commercial library.

Change History (11)

comment:1 Changed 11 years ago by adrpo

This model is wrong as if you connect two variables in an expandable connectors one of them should have been previously connected to an existing (normal) variable.
Even Dym complains. I'll try to make a better test model.

comment:2 Changed 11 years ago by sjoelund.se

  • Milestone changed from 1.9.0 to 1.9.1

Postponed until 1.9.1

comment:3 Changed 10 years ago by sjoelund.se

  • Milestone changed from 1.9.1 to 1.9.2

This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).

comment:4 Changed 10 years ago by sjoelund.se

  • Milestone changed from 1.9.2 to 1.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:5 Changed 9 years ago by sjoelund.se

  • Milestone changed from 1.9.3 to 1.9.4

Moved to new milestone 1.9.4

comment:6 Changed 9 years ago by sjoelund.se

  • Milestone changed from 1.9.4 to 1.9.5

Milestone pushed to 1.9.5

comment:7 Changed 9 years ago by sjoelund.se

  • Milestone changed from 1.9.5 to 1.10.0

Milestone renamed

comment:8 Changed 8 years ago by sjoelund.se

  • Milestone changed from 1.10.0 to 1.11.0

Ticket retargeted after milestone closed

comment:9 Changed 8 years ago by sjoelund.se

  • Milestone changed from 1.11.0 to 1.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:10 Changed 7 years ago by casella

  • Milestone changed from 1.12.0 to Future

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.

comment:11 Changed 7 years ago by casella

  • Resolution set to invalid
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.