leahi-sw.config

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LEAHI-SW-CONFIG-LDT-2825_Service - SW - 01 - Institutional - R&I
LEAHI-SW-CONFIG-LDT-2825_Service - SW - 01 - Institutional - R&I
LEAHI-SW-CONFIG-LDT-2805_Edit Treatment Parameters During Treatment - SW - 01 - Edit Treatment Parameters During Treatment - R&I
LEAHI-SW-CONFIG-LDT-2805_Edit Treatment Parameters During Treatment - SW - 01 - Edit Treatment Parameters During Treatment - R&I
Merge branch 'feature/LDT-2686-patient-vitals-enhancement' into staging

Bamboo Commit: Updated Alarms.conf

    • -161
    • +0
    /configurations/Alarms/Alarms.conf
LEAHI-SW-CONFIG-LDT-2727_Service - SW - 01 - Service - R&I
LEAHI-SW-CONFIG-LDT-2727_Service - SW - 01 - Service - R&I
LEAHI-SW-CONFIG-LDT-2686_Patient Vitals - SW - 01 - Enhancement - Round timestamp - R&I
LEAHI-SW-CONFIG-LDT-2686_Patient Vitals - SW - 01 - Enhancement - Round timestamp - R&I
LDT-2691 Patient Vitals - SW - 01 - Enhancement - Round timestamp - R&I - 05: DEV - Feature Implementation

Update conf vitals measurement interval options to align with PRS -131

    • -6
    • +9
    /configurations/Parameters/DataList.conf
Merge branch 'feature/LDT-1440-ultrafiltration' into staging

LDT-1445: Ultrafiltration - SW - 01 - R&I - 05: DEV - Feature Implementation

- Updated Parameters/DataList.conf to add Ultrafiltration volume resolution.

    • -0
    • +2
    /configurations/Parameters/DataList.conf
Merge branch 'feature/LDT-1616-headerbar-prescription' into staging

RESOLVED

RESOLVED

RESOLVED.

RESOLVED.

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

so the isActive is the internal property of ValueAdjuster and it is binded to the c++ property of <*>set. Similar to how we binded the value to the c++ property

so the isActive is the internal property of ValueAdjuster and it is binded to the c++ property of <*>set. Similar to how we binded the value to the c++ property

same

same

yes when not active you can press increment or decrement which will then show the value and set value to the default value

yes when not active you can press increment or decrement which will then show the value and set value to the default value

same?

same?

If not isActive, then canIncrement?

If not isActive, then canIncrement?

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

understood, but you have now two varables/propery for this purpose the one with _ in qml and the one with set in C++. how do they get in sync?

understood, but you have now two varables/propery for this purpose the one with _ in qml and the one with set in C++.
how do they get in sync?

I am using the *set from the VALUESET macro to sync the isActive of the 2 instances of the component

I am using the *set from the VALUESET macro to sync the isActive of the 2 instances of the component