TreatmentStack.qml

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
removed and model now lives in c++

removed and model now lives in c++

model moved to c++

model moved to c++

updated and moved

updated and moved

create model in c++ and expose to qml and let c++ handle updating model

create model in c++ and expose to qml and let c++ handle updating model

move user properties above defined properties

move user properties above defined properties

added status to list model

added status to list model

LEAHI-APPLICATION-LDT-3574_Misc SW Enhancements - SW - 01 - General Aesthetics - 02-S24 - R&I
LEAHI-APPLICATION-LDT-3574_Misc SW Enhancements - SW - 01 - General Aesthetics - 02-S24 - R&I
add element for status color

add element for status color

LEAHI-APPLICATION-LDT-3373_Misc SW Enhancements - SW - 01 - BloodPrime-02 - R&I
LEAHI-APPLICATION-LDT-3373_Misc SW Enhancements - SW - 01 - BloodPrime-02 - R&I
LEAHI-APPLICATION-LDT-3413_HDF - SW - 01 - Main-Tx HDF Tab - Graph - R&I
LEAHI-APPLICATION-LDT-3413_HDF - SW - 01 - Main-Tx HDF Tab - Graph - R&I
LEAHI-APPLICATION-LDT-3393_HDF - SW - 01 - Main-Tx HDF Tab - R&I
LEAHI-APPLICATION-LDT-3393_HDF - SW - 01 - Main-Tx HDF Tab - R&I
Updated.

Updated.

Add comment for why using * 2 (look & feel)

Add comment for why using * 2 (look & feel)

No longer needed since staging was changed.

No longer needed since staging was changed.

Updated.

Updated.

Updated.

Updated.

User waited too long would follow the same rejected behavior, do we still need to show the specific rejection path for the user waiting too long?

User waited too long would follow the same rejected behavior, do we still need to show the specific rejection path for the user waiting too long?

Updated.

Updated.

Updated.

Updated.