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
I've come across several cases where "deep modifications" are used. An example would be this fragment from OpenHydraulics.Circuits.PressureCompensated:
A better approach would be to "propagate" the parameters like portA.p.start and P2A.table up one level. This has two advantages. First, it adds those parameters to the dialog for V4_3CC (and potentially others, depending on where in the inheritance tree they the parameters are introduced) and it avoids having to remember how to make these deep modifications each time you create a new instance of V4_3CC. Otherwise, users have to do something like "Show Component" in Dymola and explore the whole hierarchy for these important parameters.
I've come across several cases where "deep modifications" are used. An example would be this fragment from
OpenHydraulics.Circuits.PressureCompensated
:A better approach would be to "propagate" the parameters like
portA.p.start
andP2A.table
up one level. This has two advantages. First, it adds those parameters to the dialog forV4_3CC
(and potentially others, depending on where in the inheritance tree they the parameters are introduced) and it avoids having to remember how to make these deep modifications each time you create a new instance ofV4_3CC
. Otherwise, users have to do something like "Show Component" in Dymola and explore the whole hierarchy for these important parameters.Ideally, the above code should really look like:
Of course, these should be organized into tabs and groups.
The text was updated successfully, but these errors were encountered: