MainStack.qml

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
remove lock diasbaled

remove lock diasbaled

switch buttons Cancel: Stay on treatment Confirm: End Treatment

switch buttons
Cancel: Stay on treatment
Confirm: End Treatment

revert this always enable lock enabled

revert this always enable lock enabled

enable lock icon

enable lock icon

make this a bool and update internally

make this a bool and update internally

keep lock button enabled and update logic

keep lock button enabled and update logic

revert this

revert this

revert cancel button to older design

revert cancel button to older design

only update size on EndTreatmentDialog and leave this size as is. and fiz settings confirm dialogs

only update size on EndTreatmentDialog and leave this size as is. and fiz settings confirm dialogs

add comment

add comment

same as above

same as above

only run when visible

only run when visible

LEAHI-APPLICATION-LDT-3000_End of Treatment - SW - 01 - R&I
LEAHI-APPLICATION-LDT-3000_End of Treatment - SW - 01 - R&I
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?