Opened 10 years ago

Last modified 3 years ago

#2926 assigned defect

Check uses-annotation on loadFile

Reported by: Martin Sjölund Owned by: Per Östlund
Priority: blocker Milestone: 1.19.0
Component: Frontend Version: trunk
Keywords: Cc:

Description

The front-end will now load models from the uses-annotation of a package.mo when loadFile is used. To disable this behaviour, use loadFile("M/package.mo", uses=false).

Change History (22)

comment:1 by Martin Sjölund, 10 years ago

Milestone: 1.9.11.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:2 by Martin Sjölund, 10 years ago

Milestone: 1.9.21.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:3 by Martin Sjölund, 9 years ago

Milestone: 1.9.31.9.4

Moved to new milestone 1.9.4

comment:4 by Martin Sjölund, 9 years ago

Milestone: 1.9.41.9.5

Milestone pushed to 1.9.5

comment:5 by Martin Sjölund, 9 years ago

Milestone: 1.9.51.10.0

Milestone renamed

comment:6 by Martin Sjölund, 8 years ago

Milestone: 1.10.01.11.0

Ticket retargeted after milestone closed

comment:7 by Martin Sjölund, 8 years ago

Milestone: 1.11.01.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:8 by Francesco Casella, 7 years ago

Milestone: 1.12.0Future

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:9 by Dietmar Winkler, 7 years ago

Unfortunately the automatic loading does not work when the libraries are stored as simple file.

Minimal example:
A.mo:

package A
  annotation (uses(B));
end A;

B.mo:

package B
end B;

Opening A.mo should load package B automatically.

It is quite annoying since I often distribute some complex libraries as a single file to new beginners who should work on "A" and which depends on "B".

comment:10 by Dietmar Winkler, 7 years ago

Milestone: Future1.13.0

comment:11 by Dietmar Winkler, 7 years ago

Owner: changed from somebody to Martin Sjölund
Status: newassigned

comment:12 by Dietmar Winkler, 7 years ago

As OMEdit 1.13.0~dev-113-g8c6364e this still does not work.

I even have the current path . in my User Libraries path setup which should add the current directory to the MODELICAPATH. But this does not seem to work. In general having that setting should not be necessary as one expects that the directory from which a library is loaded is also added to the MODELICAPATH. At least this is the common behaviour that other tools have.

comment:13 by Francesco Casella, 6 years ago

Milestone: 1.13.01.14.0

Rescheduled to 1.14.0 after 1.13.0 releasee

comment:14 by Francesco Casella, 5 years ago

Priority: highblocker

@sjoelund.se, can we fix this issue for good in 1.14.0? Shouldn't be too hard.

comment:15 by Francesco Casella, 5 years ago

Milestone: 1.14.01.15.0

Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2.

This issue, previously marked as blocker for 1.14.0, is rescheduled to 1.15.0

comment:16 by Francesco Casella, 5 years ago

Milestone: 1.15.01.16.0

Release 1.15.0 was scrapped, because replaceable support eventually turned out to be more easily implemented in 1.16.0. Hence, all 1.15.0 tickets are rescheduled to 1.16.0

comment:17 by Francesco Casella, 5 years ago

@sjoelund.se, can we fix this alongside the package manager?

comment:18 by Francesco Casella, 4 years ago

Milestone: 1.16.01.17.0

Retargeted to 1.17.0 after 1.16.0 release

comment:19 by Francesco Casella, 4 years ago

Owner: changed from Martin Sjölund to Per Östlund

@perost, could you please take care of this?

comment:20 by Francesco Casella, 4 years ago

Milestone: 1.17.01.18.0

Retargeted to 1.18.0 after 1.17.0-dev.beta2 release

comment:21 by Francesco Casella, 3 years ago

Milestone: 1.18.0

Ticket retargeted after milestone closed

comment:22 by Francesco Casella, 3 years ago

Milestone: 1.19.0

1.18.0 blocker tickets moved to 1.19.0

Note: See TracTickets for help on using tickets.