Menu
▾
▴
#39 The Configuration editor does not set currentDir to the loc
The Configuration editor does not set currentDir to the location of OMI file
I version 1.4.0 of the configuration editor, the current directory for the individual LinkableComponents in a configuration was set to the location of the associated OMI files. This was very convenient, because components could easily find location of input and output files relative to the OMI file. Unfortunately, in version 1.4.1 of the configuration Editor, current dir is the location of the configuration editor it selves. It is naturally possible to put the full file path to the location of files into the OMI file. But then it becomes problematic if someone moves the OMI files and model input files to another location. So, my recommendation is to put the nice feature for setting the currentDir back into future releases of the configuration editor.
Kind regards
Jan Gregersen
Remark: I know that are associated issues for discussion. E.g: As a component provider, how can you be sure that a configuration editor actually sets the currentDir to the location of the OMI file? Well, currently you cannot be sure of that, simply because it is not defined in the OpenMI standard that a configuration editor should behave like that. And therefore, in principle, you cannot take advantage of it when you implement you component. So, maybe for version 2 it would be wise to consider if behaviour of configuration editors should be included in the standard (So, far problems like that has not been seen because most people are using the configuration editor provided by OATC, which has made the behaviour to this editor the defacto standard for configuration editors). I assume that if we investigate further, we will find more similar issues related to configuration editors or more generally to loading LinkableComponents.
This has missed the cut for 1.4.1 and so will be reconsidered for 1.4.2 or 2.0