mirror of
https://github.com/OPM/ResInsight.git
synced 2026-10-25 22:50:25 -05:00
Kristian Bendiksen
3a1ff7a1e3
Combined filters used to always show whatever literal string the user passed in (or the default "Combined Filter"). For programmatic creation without a name, that string never reflected the children, leaving the case-level "Data Filters" tree row stale when child bounds changed. Add an m_autoDeriveName flag (default true) to RimCombinedFilter. When on, the display name is recomputed on every relevant change — addFilter, removeFilter, onChildAdded, onChildFilterChanged, and combineMode toggle — by joining children's name() with " AND " / " OR ". The flag flips to false the first time the user renames the filter via the UI property panel or via Python (combined.user_description = "..."), preserving any explicitly typed name verbatim from then on. Two child-creation paths needed an extra triggerFilterChanged() so the combined parent recomputes after the child's final name is set: addPropertyFilterToCombinedFilter (setDefaults updates name without a signal) and RimcCombinedFilter_addRangeFilter (Rimc applies user params after addNewFilter). The Rimc factory passes setAutoDeriveName(false) only when a name is supplied. The Python example demonstrates both modes side by side, and test_combined_filter.py adds three cases: named filter preserves its name, auto-derived filter tracks bound mutations, and Python rename locks the auto-derived filter.