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 fcasella on 25 Jul 2012 20:58 UTC
Table-based functions and signal generators can use files as data sources. Currently, the pathname is either absolute, or relative to the current working directory. It is therefore not possible to reference pathnames relative to the library base path, which is essential for portability across different PCs and filesystems.
The proposal is to allow modelica:// URIs in filenames, both in the Table components and in all the functions dealing with files in the Modelica.Utilities package.
Comment by otter on 4 Oct 2012 12:34 UTC
Fixed in 3c0057c98c16b7688cf857040b7f5b8cee670109 by introducing a tool specific function "loadResource" in ModelicaServices and calling this function from the table models (the file names can now be given as an URI). Additionally, URI support is added for functions that treat a file as one complete entity, in particular:
In all other cases, the user has to explicitly first transform the URI name to an absolute path name with new function
Modelica.Utilities.Files.loadResource
The reason is that, e.g., if a function like print or readLine would accept URIs, then for every call the absolute path name would need to be determined.
Reported by fcasella on 25 Jul 2012 20:58 UTC
Table-based functions and signal generators can use files as data sources. Currently, the pathname is either absolute, or relative to the current working directory. It is therefore not possible to reference pathnames relative to the library base path, which is essential for portability across different PCs and filesystems.
The proposal is to allow modelica:// URIs in filenames, both in the Table components and in all the functions dealing with files in the Modelica.Utilities package.
Migrated-From: https://trac.modelica.org/Modelica/ticket/785
The text was updated successfully, but these errors were encountered: