Behrouz NematiPour

Since this is being used everywhere, I would recommend defining a global variable(s) so that we can later be flexible to adjust that for all the mouse clicks or watforobject functions

Since this is being used everywhere, I would recommend defining a global variable(s) so that we can later be flexible to adjust that for all the mouse clicks or watforobject functions

Shouldn't this function be defined in a more general location/file? And same comment here to be aware of the translation flexibility for later.

Shouldn't this function be defined in a more general location/file?
And same comment here to be aware of the translation flexibility for later.

Not able to find in your test.py, but these types of texts will change with the translation, and if the text is used as has been defined here, your test will fail in other languages. Just be aware ...

Not able to find in your test.py, but these types of texts will change with the translation, and if the text is used as has been defined here, your test will fail in other languages.
Just be aware and think of a solution to be flexible for later when testing with other languages.

It is a little bit concerning: Could you please test/describe the following scenarios: *What if we have more than one Heparin type supported? *What if none (incorrectly) has been defined in the c...

It is a little bit concerning:
Could you please test/describe the following scenarios:

  • What if we have more than one Heparin type supported?
  • What if none (incorrectly) has been defined in the configuration (do we get an index out of bounds)?
We will address this later on code modularizations. RESOLVED.

We will address this later on code modularizations.
RESOLVED.

I believe any related view could have provided a timer since they are inherited from QObject. That is fine for now but consider using our C++ view codes for such a thing.

I believe any related view could have provided a timer since they are inherited from QObject.
That is fine for now but consider using our C++ view codes for such a thing.

Thank you .

Thank you .

Please align.

Please align.

Please use the mainTreatment screen as the default. If necessary, could you create a specific enum to clean up the stack (which I do not believe is needed.)

Please use the mainTreatment screen as the default.
If necessary, could you create a specific enum to clean up the stack (which I do not believe is needed.)

You no longer need this after you move the heparin screen from the sections folder.

You no longer need this after you move the heparin screen from the sections folder.

Shouldn't ""Unfractionated 1000"" come from the configurations?

Shouldn't ""Unfractionated 1000"" come from the configurations?

We should add the qsTr()

We should add the qsTr()

Move this outside of the sections folder, since it is no longer a section and has its own dedicated screen.

Move this outside of the sections folder, since it is no longer a section and has its own dedicated screen.

We should use "min" for minutes and not "mins". Same for "hrs" => "hr".

We should use "min" for minutes and not "mins".
Same for "hrs" => "hr".

What is this file used for? And please add a brief description for the file comment.

What is this file used for?
And please add a brief description for the file comment.

Please put comments for your division number.

Please put comments for your division number.

statusColor is so general, but is bound to the heparinStatusColor. Please either change the status color to be heparin only or change the heparinStatus Color name to be more general. The latter is ...

statusColor is so general, but is bound to the heparinStatusColor.
Please either change the status color to be heparin only or change the heparinStatus Color name to be more general.
The latter is better.

No Action For Now: Same for the vError param: https://devapps.diality.us/cru/#LEAHI-APPLICATION-LDT-2727-1CFR-76762

No Action For Now:
Same for the vError param:
https://devapps.diality.us/cru/#LEAHI-APPLICATION-LDT-2727-1CFR-76762

No Action For Now: Please always use mError, since it is local to the script function, to be consistent with the rest. Also, usually it is a number, not a bool. It is fine for now, but later we sh...

No Action For Now:
Please always use mError, since it is local to the script function, to be consistent with the rest.
Also, usually it is a number, not a bool.

It is fine for now, but later we should create a decorator to cover these types of similarities.

This does not entirely follow the standard. But it is fine since we do not have the Bluetooth feature implemented yet. Standard format example

This does not entirely follow the standard.
But it is fine since we do not have the Bluetooth feature implemented yet.
Standard format example

Please use the following commands from NetworkManager utilities, since in Leahi we are not using the wpa_supplicant directly: nmcli connection delete DilaityIoT nmcli connection delete $(nmcli -t...

Please use the following commands from NetworkManager utilities, since in Leahi we are not using the wpa_supplicant directly:

nmcli connection delete DilaityIoT 
nmcli connection delete $(nmcli -t -f NAME connection show --active)