Opened 11 years ago
Closed 7 years ago
#2407 closed defect (worksforme)
Invalid component reference for model hierarchy with identical names when using Inner/outer
Reported by: | petar | Owned by: | somebody |
---|---|---|---|
Priority: | critical | Milestone: | 1.12.0 |
Component: | Frontend | Version: | trunk |
Keywords: | Cc: |
Description
The attached model (A very simple MultiBody example), produces the following line in the flat dae:
input Real pendulum.pendulum.specularCoefficient(min = 0.0) = pendulum.pendulum.world.defaultSpecularCoefficient
But there is no variable named
pendulum.pendulum.world.defaultSpecularCoefficient
The correct name should be
pendulum.world.defaultSpecularCoefficient
The problem can be avoided by changing the outermost instance to e.g. pendulum1.
Attachments (1)
Change History (13)
Changed 11 years ago by petar
comment:1 Changed 11 years ago by sjoelund.se
- Milestone changed from 1.9.0 to 1.9.1
comment:2 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:3 Changed 9 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:4 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:5 Changed 9 years ago by sjoelund.se
- Milestone changed from 1.9.4 to 1.9.5
Milestone pushed to 1.9.5
comment:6 Changed 9 years ago by sjoelund.se
- Milestone changed from 1.9.5 to 1.10.0
Milestone renamed
comment:7 Changed 8 years ago by sjoelund.se
- Milestone changed from 1.10.0 to 1.11.0
Ticket retargeted after milestone closed
comment:8 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:9 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:10 Changed 7 years ago by casella
- Resolution set to invalid
- Status changed from new to closed
Save Total files cannot be opened by OMC as they are not valid Modelica
comment:11 Changed 7 years ago by sjoelund.se
- Milestone changed from Future to 1.12.0
- Resolution invalid deleted
- Status changed from closed to reopened
comment:12 Changed 7 years ago by sjoelund.se
- Resolution set to worksforme
- Status changed from reopened to closed
Ignore @casella's comment. OMC opens total files just fine. Only OMEdit does not. And the model is fine right now.
Postponed until 1.9.1