LockDialog.qml

Clone Tools
  • last updated a few seconds 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
LEAHI-APPLICATION-LDT-1516_Feature/Ldt 1516 Headerbar Component
LEAHI-APPLICATION-LDT-1516_Feature/Ldt 1516 Headerbar Component
RESOLVED

RESOLVED

i removed the comment to be more clear

i removed the comment to be more clear

RESOLVED

RESOLVED

yes i agree makes more sense that way of whats going on.. I moved this to where they are being instantiated

yes i agree makes more sense that way of whats going on.. I moved this to where they are being instantiated

Sorry, yes you are correct, it is just using the defaults. Should the commented portion be removed though?

Sorry, yes you are correct, it is just using the defaults.
Should the commented portion be removed though?

Generally, any anchoring/positioning properties for the top level item should be set in the parent object where this object is being instantiated since any changes to these properties in the parent...

Generally, any anchoring/positioning properties for the top level item should be set in the parent object where this object is being instantiated since any changes to these properties in the parent will be overridden here and it may not be obvious that it is happening.

this still does the affect. I believe if you leave the property animation empty it will animate all changes of whatever Behavior is on. Refer https://doc.qt.io/archives/qt-5.15/qml-qtquick-property...

this still does the affect. I believe if you leave the property animation empty it will animate all changes of whatever Behavior is on. Refer https://doc.qt.io/archives/qt-5.15/qml-qtquick-propertyanimation.html

Stephen Quong I belive it is still effective, Isn't it Nicholas Ramirez ?

Stephen Quong
I belive it is still effective,
Isn't it Nicholas Ramirez ?

Remove line since effective code is commented out.

Remove line since effective code is commented out.

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

removed

removed