However, I present an easy and clean solution that overcomes any possible issue and avoids OpenModelica to run with new frontend (still quite unmature).
I think that convoluted code should be avoided whenever possible.
The problem is that in VisualizeSimpleRoads the road was declared as outer even though the VisualizeSimpleRoads model was part of a road itself. This was causing issues in OpenModelica that was not able to solve for an outer component asked from a model that is part of the outer component itself.
Please consider if this change would or would not make the library easier and cleaner.
If not, please drop my pull request.
Following https://github.com/modelica/VehicleInterfaces/issues/18 the issue does not appear to be there in OpenModelica using the
-d=newInst
flag.However, I present an easy and clean solution that overcomes any possible issue and avoids OpenModelica to run with new frontend (still quite unmature). I think that convoluted code should be avoided whenever possible.
The problem is that in VisualizeSimpleRoads the road was declared as
outer
even though the VisualizeSimpleRoads model was part of a road itself. This was causing issues in OpenModelica that was not able to solve for an outer component asked from a model that is part of the outer component itself.Please consider if this change would or would not make the library easier and cleaner. If not, please drop my pull request.