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)?
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.
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.)
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: 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.
