sources

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-13049 - UI Treatment Parameters Entry: Some values for treatment parameter entry on treatment parameter entry screen in create treatment do not match SRS/PRS

- There was a bug in the fix which was related to the validation and caused to fail the treatment parameters validation.

- also removed the disable if the SD is not detected correctly. (QStorageInfo is not sending DeviceReady correctly)

- enabled the float rounding to 3 in the log

- Enabled the Create Treatment button rejection notification, since it seems it is not being handled by alarms as presumed.

- Fixed the BloodPressure interval value to display OFF when set to zero.

DEN-9129: Unable to proceed past "Create a Custom Treatment" when Arterial and Venous Pressure (High) Limits maximum values are initially selected

Also modified the SliderCreateTreatment.qml to show by the default the zero value not the OFF since it is only two Heparin Bolus/Dispensing which display OFF for zero value.

    • -0
    • +2
    ./gui/qml/components/GridSelection.qml
DEN-13049: UI Treatment Parameters Entry: Some values for treatment parameter entry on treatment parameter entry screen in create treatment do not match SRS/PRS

Bamboo Commit: Updated MAlarmMapping.cpp

Bamboo Commit: Updated MAlarmMapping.cpp

Bamboo Commit: Updated MAlarmMapping.cpp

Bamboo Commit: Updated MAlarmMapping.cpp

DEN-12836: Treatment Report/log export modifications

- A little cleanup and refactoring and added the treatment log 10% rotation.

DEN-13199: INT: DVT Support

- During DVT support found out the BCuff vitals debug item on the top of the screen is not working, and fixed ti by adding a real time version of the same actual vital properties which gets updated every time the vitals received.

    • -10
    • +10
    ./model/hd/alarm/MAlarmMapping.cpp
  1. … 2 more files in changeset.
RESOLVED.

RESOLVED.

Bamboo Commit: Updated MAlarmMapping.cpp

Sure Sean, if that is the decision, will do it soon and create a case for that. I also believe some other CL Switches need to be removed, which were only implemented for our testing at the time (CA...

Sure Sean, if that is the decision, will do it soon and create a case for that.
I also believe some other CL Switches need to be removed, which were only implemented for our testing at the time (CANBus).

Issue DEN-13441 - MR: Make the Dialin log permanent with no switch [CL switches review/removal] has been successfully created

Bamboo Commit: Updated MAlarmMapping.cpp

Bamboo Commit: Updated MAlarmMapping.cpp

If this is to log Dialin messages, we should always do that (no switch). If a Dialin command is given/responded to, we definitely want to know about that - so want to see it in the log. Dialin comm...

If this is to log Dialin messages, we should always do that (no switch). If a Dialin command is given/responded to, we definitely want to know about that - so want to see it in the log. Dialin commands are always one-shot type messages, so will not impact log size.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED

RESOLVED

Bamboo Commit: Updated MAlarmMapping.cpp

This code is going to be used later in the Log Export for slow transfer & confirmation for the USB port slow transfer issue. I kept it in the application repo to keep it safe. Commented out to not ...

This code is going to be used later in the Log Export for slow transfer & confirmation for the USB port slow transfer issue.
I kept it in the application repo to keep it safe.
Commented out to not affect the coverage.

UI-DEN-12716 : UI-DEN-12716-2 : UI-DEN-12716_UI BN S70

- Addressed the code review comments.

- The timedatectl command was missing the set-timezone command option.

- When using timedatectl no need to use the hwclock

- During the unit test review noticed that the thread name changed and updated and kept it, although we still have some issues there which needs to be fixed.

    • -26
    • +26
    ./cloudsync/CloudSyncController.h
  1. … 3 more files in changeset.
http://dvm-linux02:8060/cru/#UI-DEN-12716-2CFR-30978 in PostTreatmentReview.qml@40

http://dvm-linux02:8060/cru/#UI-DEN-12716-2CFR-30978
in PostTreatmentReview.qml@40

Where would this value change?

Where would this value change?

At the moment I added that switch I assumed it should only be used for V&V and SysV testing.

At the moment I added that switch I assumed it should only be used for V&V and SysV testing.

This is the requirement. PRS 417: The HD Device manufacturing default timezone shall be (UTC-08:00) Pacific Time.

This is the requirement.
PRS 417: The HD Device manufacturing default timezone shall be (UTC-08:00) Pacific Time.

Why is main.cpp all commented out?

Why is main.cpp all commented out?

All systems will be setup for Pacific time zone?

All systems will be setup for Pacific time zone?

Why must this be removed later?

Why must this be removed later?