Used to match with prev naming convention and also low and high temperature limits are checked here
Added
Removed
I don't see fix. I'm resolving this comment, but I added another comment that hopefully clarifies the issue.
Move registration back to VView.h
Update function header to include message param.
Why are we checking only fresh side pressures and not spent side as well?
Fix comment.
make format for advanced in Vsettings
coment with current resolution this make the screen look nice
Remove reset override functions. Reset should be handled in the single (general) override command handler.
do you need to also register the following that are imported in main.qml? VTreatmentAdjustmentBolusVolume VTreatmentAdjustmentDurationEdit VTreatmentAdjustmentDurationConfirm VTreatmentAdjustmentSetPoints VTreatmentAdjustmentBloodFlowRate VTreatmentAdjustmentDialysateFlowRate VTreatmentAdjustmentDialysateTemperature
Properties are being set to zero by default.
Updated.
changed this Ultrafiltration in one line
done
followed the pattern.
If there are no messages from the BloodLeak.h then we should remove the include.
Fixed
Updated the test scripts as per the suggestion
added comment
fixed it
Remove extra blank line.
Add space between (( and )).
spelling error should be "title"
Updated the value to all combo boxes
Updated the value to 120
Only need 2 message IDs here. In Leahi, we don't have separate messages for set vs. reset. Both set and reset are handled in the same message.
Remove "Set" from override function names. These 2 override functions should handle both set and reset (from msg payload).
View still exists, instance has been moved to main.qml
changed.
Updated
M3 or P10 ? need a good documentation
sensor name required in comments
If this function is only called from here, should we just move the function's code into this function (i.e. combine the functions)?
Update to TD.
lets reduce this to 3. we do not need to test this many variations
reduce this to 3 variations as well
I thought we were going to complete cycle when done (not based on time) and feed back error in cycle time to control D48 pump speed to reduce error going forward so we end up getting the target cycle time which will give us target flow rate.
can we change to just click the arrow button just once as we do not care about what is being set. We only care about the bp measurement parameter
With exception of D4 temperature, is there any reason why all other temperatures shouldn't be filtered the same way?
This is still used. It will be removed in the new branch.
It looks like it's still here.
Is this line expected here?
Got a suggestion or an issue? Discuss it on the Atlassian Community or visit Atlassian Support for other options.
