application

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Adding the Acknowledge initialize log

    • -0
    • +1
    /sources/canbus/MessageAcknowModel.cpp
DEN-9897: Recirculate confirm button click doesn't do anything.

- After rinseback completes during treatment, UI does not provide option to go back to treatment after RECONNECT

- It has been fixed to send message 84.1 for the confirm

    • binary
    /resources/images/Omron-bp7000.png
DEN-9691: UI Strings Do Not Fit Various Treatment Screens

- Used abbreviation for some long Treatment parameters name, provided by Clayton

Bamboo Commit: Updated ui_build_history.log with build number and build date

Merge branch 'DEN-9626UI_DEV_BluetoothCuffIntegration' into develop

DEN-9418: Code Review 0

- Cherry picked the code review updated from post branch

- Correcting the message IDs enum comments.

    • -18
    • +18
    /sources/canbus/MessageGlobals.h
DEN-9418: Code Review 0

- Cherry picked the code review updated from post branch

- Function comments.

- Removed unused BLE alarm from alarm generator.

DEN-9707: BP/HR empty measurement display does not match PRS

- alarm mapping update.

- post code review applied here.

    • -12
    • +14
    /sources/model/hd/alarm/MAlarmMapping.cpp
DEN-9418: Code Review 0

- DEN-9707: BP/HR empty measurement display does not match PRS

- Updated Alarms Mapping

    • -2
    • +2
    /sources/model/hd/alarm/MAlarmMapping.cpp
RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

Updated.

Updated.

Added.

Added.

Added.

Added.

Added.

Added.

Added.

Added.

DEN-9418: Code Review 0

It has been removed. We should reserve our Alarm System mostly for critical HW issues during treatment.

It has been removed.
We should reserve our Alarm System mostly for critical HW issues during treatment.

RESOLVED.

RESOLVED.

I mean, all others appear to be in the following order: 1) number of params and 2) size of params. So to be consistent, shouldn't this be 1 * 15 (1 param, 15 bytes)?

I mean, all others appear to be in the following order: 1) number of params and 2) size of params.
So to be consistent, shouldn't this be 1 * 15 (1 param, 15 bytes)?

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.