Draft: Resolve "Sort out component-index handling in devel"
- Sep 03, 2021
-
-
Utz-Uwe Haus authoredeb143385
-
Utz-Uwe Haus authored876b7220
-
Utz-Uwe Haus authorede19ded1d
-
Utz-Uwe Haus authored6d271299
-
- Aug 06, 2021
-
-
Utz-Uwe Haus authored
PM needs to do the right bookkeeping to understand a re-JOIN is not a duplicate join.
4549720a -
Utz-Uwe Haus authored
This fixes the user-side detection of duplicate JOINs (components re-using other component's names/index pair). Also cleans up duplicate state keeping variable representing PM/no-PM case: We now use g_mstro_pm_attached as the sole source of truth.
146066b0
-
- Aug 05, 2021
-
-
Utz-Uwe Haus authoredd80ed41e
-
Utz-Uwe Haus authorede9a4f81f
-
Utz-Uwe Haus authored404dc7c7
-
- Aug 04, 2021
-
-
Ali Mohammed authored
add test for two clients with same workflow, component name, and component ID + test for client init and finalize and enter again
534e9f77
-