You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by beutlich on 26 Jun 2013 08:37 UTC
Revision caf6227 set the table file name string parameter to always be evaluated. This, however is not acceptable for some SimulationX users. In the past we had the requirement to run variant calculations of the C-code exported model on the table file name. This feature is now broken. I also believe that caf6227 is not backward compatible with MSL 3.2.
Comment by otter on 27 Jun 2013 10:33 UTC
Fixed in 0052a94 and 6748be6:
The issue is that loadResource(..) was included at several location in models, in order to conveniently support URIs for file names. However, the drawback is that some tools might need to evaluate loadResource at compile time, and this might not be always be possible in all situations. The fix removes all (generic) loadResource(..) calls from the models and a user has to use it explicitely to construct a file name. By this it is guaranteed that existing models/libraries will work. There are some examples and defaults where loadResource(..) is used and reference files under Modelica/Resources. This occurences are kept since otherwise these files cannot be read in a reliable way and these uses of loadResource are uncritical.
Furthermore, ModelicaTest.Tables was adapted by including explicit loadResource(..) calls.
Reported by beutlich on 26 Jun 2013 08:37 UTC
Revision caf6227 set the table file name string parameter to always be evaluated. This, however is not acceptable for some SimulationX users. In the past we had the requirement to run variant calculations of the C-code exported model on the table file name. This feature is now broken. I also believe that caf6227 is not backward compatible with MSL 3.2.
Migrated-From: https://trac.modelica.org/Modelica/ticket/1178
The text was updated successfully, but these errors were encountered: