This behaviour, although correct, and clear once one has understood what happens, can be very confusing in the beginning. go in the modeling perspective, double click on the FMU and change gain1_k from 2 to 4, and simulate => the output is still 2 (again, this is because K=2 is hard-coded in the FMU). This is because in reality K=2 was hardcoded in the FMU change K from 2 to 4 in the variables Browser => the output does not change to 4. simulate: the output is (correctly) constantly equal to 2 load the FMU, open Test and connect the output of realExpression to the FMU input When we later use the FMU, no trace of this characteristic is there. ModeliaBuiltin which will involve some redesign.' petfrД¦071 'Don't show parameter edits in FMU created with ''Evaluate all parameters'''ДџMI v1.16.0-dev defect lochel assigned T11:50:02+02:00 T21:50:28+02:00 'When we create an FMU while ''Evaluate all parameters'' is active, parameter values are hard-coded in the FMU. Including small examples, right now, before moving it to We can start now by documenting the existing interactive module API Martin had been suggesting this from a very long time now. We should move all the stuff from interactive to CevalScript & ModelicaBuiltin. The only problem is that it doesnвЂ™t include the interactive module which is almost half of the scripting environment. OpenModelica scripting environment is already documented. This is important for eliminating some bugs and misunderstandings as used between OMEdit and OMC), and in the longer term redesign part of it to make it more consistent. * look for ``, keep only the ''last'' instance' dietmarwДў221Дќocumentation of Scripting and Communication Protocol Interactive Environment trunk defect somebody new T15:00:05+02:00 T15:01:49+02:00 'Дocument the current OM scripting and communication protocol * look for ``, keep first instance and discard all following. At the same time only keep one ` ` (otherwise there will be a warning again) ` and if more than one then merge the content into one. Solution could look like something like this: Funnily enough in `2` the ` ` tags have been removed which means no warnings in from tidy. Now the one file that is almost always going to cause this problem is the `ModelicaLicense2` class because the template has exactly this structure. It seems that two head sections are not such a big problem but tidy does not like to have content after the `` tag. ` section in the info layer then the resulting HTML will contain two of them. Sections correctlyД›uild Environment trunk defect new T01:21:30+02:00 T23:08:53+01:00 'I noticed a small problem with the documentation generation script `GenerateDoc.mos`:

Code hs 2.7.9