Opened 10 years ago
Last modified 3 years ago
#3287 new enhancement
Allow input of common parameters and replaceable classes in a multiple component selection
| Reported by: | Francesco Casella | Owned by: | Adeel Asghar |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | OMEdit | Version: | trunk |
| Keywords: | Cc: |
Description
It is often the case that a model contains several components for which some parameter(s) must take the same value. In this case, it is very convenient to be able to select the set of components and input the value(s) of the parameter(s) in common only once.
Once replaceable class support is in place (see #2079), this should also apply to replaceable classes. In particular, this feature will allow to change the medium model of all the Modelica.Fluid components of a system sharing the same medium with just one selection and a few clicks of the mouse.
Attachments (2)
Change History (16)
comment:1 by , 10 years ago
| Type: | defect → enhancement |
|---|
comment:2 by , 10 years ago
by , 10 years ago
| Attachment: | TestMultipleComponents.mo added |
|---|
comment:3 by , 10 years ago
The electrical circuit has one resistor R1 and one inductor G1 with some parameters in common (T_ref, T, alpha, useHeatPort). If you select both components at the same time, it would be nice being able to set those parameters only once.
We also need to deal with the case where the common parameters already have different values set. Any solution would be ok in this case, as long as a) the existing values are not lost, and b) it is possible to reset them with a single action if needed. See the second attachment
by , 10 years ago
| Attachment: | TestMultipleComponents2.mo added |
|---|
comment:8 by , 8 years ago
| Milestone: | 1.11.0 → 1.12.0 |
|---|
Milestone changed to 1.12.0 since 1.11.0 was released.
comment:9 by , 7 years ago
| Milestone: | 1.12.0 → 1.13.0 |
|---|
comment:11 by , 5 years ago
| Milestone: | 1.14.0 → 1.16.0 |
|---|
Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0
comment:13 by , 4 years ago
| Milestone: | 1.17.0 → 1.18.0 |
|---|
Retargeted to 1.18.0 because of 1.17.0 timed release.
It would nice if you can provide a test case or a simple example.