application

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-15813 UI: Decommission cloud token removal

    • -42
    • +59
    /sources/cloudsync/CloudSyncController.h
Removed.

Removed.

DEN-16037: Updated - System does not Erase Treatment Logs When Folder is Full

Remove unneeded const char in the header

missing if braqckets

missing if braqckets

missing if {} brackets

missing if {} brackets

Please remove this as well, regarding the changes made in CPP

Please remove this as well, regarding the changes made in CPP

UI-DEN-16181_UI VD S103 IO_Fail_Alarm [ READY ]
UI-DEN-16181_UI VD S103 IO_Fail_Alarm [ READY ]
DEN-13474: Updated - UI: SRSUI for SD-Card/File System Write Failure & Export Log Failure may be Outdated from PRS (SRSUI 1077-1079)

Change alarm handling for onLogIOFail case

DEN-14815: Cartridge Removal Screen is Displayed Prematurely

- Added the QML code.

DEN-14815: Cartridge Removal Screen is Displayed Prematurely

- Added the Response model and updated the view for MAdjustPatientDisconnectionConfirmResponse

    • -2
    • +3
    /sources/canbus/MessageInterpreter.cpp
DEN-14815: Cartridge Removal Screen is Displayed Prematurely

- Added the message ID_AdjustPatientDisconnectionConfirmReq = 0x0600, // 6

    • -2
    • +14
    /sources/canbus/MessageDispatcher.cpp
    • -0
    • +1
    /sources/canbus/MessageInterpreter.cpp
DEN-14815: Cartridge Removal Screen is Displayed Prematurely

- Modified the Patient Disconnection confirm to notify since there is no response and UI just notifies the HD.

- This way the actual confirm which is on the Treatment Review screen Next button can have better name.

- Also modified the ID_AdjustDisposablesRemovalConfirmRsp enum to match its req.

    • -2
    • +2
    /sources/canbus/MessageInterpreter.cpp
DEN-16123-UI-BN-S103-PostHeparin
DEN-16123-UI-BN-S103-PostHeparin
DEN-15911: Post-treatment screen displays heparin type and heparin concentration even if heparin rate and dispensing were disabled in pre-treatment

- Separated the Log and the Gui values for now to address the cloud log later, when the cloud is ready to not to reject Logs to have NONE.

    • -37
    • +49
    /sources/storage/TreatmentLog.cpp
DEN-15112: Added - UI: UI Does not Display (Pending) Treatment Logs on Export Logs Screen

Add the log list model for SD card and USB in CPP

Updated the SettingLogExport QML to reflect CPP model addition

    • -0
    • +258
    /sources/view/settings/VLogFileListModel.cpp
    • -0
    • +101
    /sources/view/settings/VLogFileListModel.h
[ On Hold - P1B ] UI-DEN-16181_UI VD S103 Filemodel
[ On Hold - P1B ] UI-DEN-16181_UI VD S103 Filemodel
Bamboo Commit: Updated MAlarmMapping.cpp

    • -14
    • +20
    /sources/model/hd/alarm/MAlarmMapping.cpp
Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

    • -20
    • +14
    /sources/model/hd/alarm/MAlarmMapping.cpp
Bamboo Commit: Updated MAlarmMapping.cpp

    • -14
    • +20
    /sources/model/hd/alarm/MAlarmMapping.cpp
Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

    • -20
    • +14
    /sources/model/hd/alarm/MAlarmMapping.cpp
DEN-16037: Updated - System does not Erase Treatment Logs When Folder is Full

Remove unnecessary newline added

Done

Done

After our conversation, I have changed as requested.

After our conversation, I have changed as requested.

Changed as requested

Changed as requested

Changed as requested

Changed as requested

I have removed the added and using the Settings_Path()

I have removed the added and using the Settings_Path()

DEN-16037: Updated - System does not Erase Treatment Logs When Folder is Full

Updated code based on CR requests

- add signals to follow device<device>StateChange and device<device>SpaceChange

- Add proper handling of the added signals (slots and connections)

- remove the added encrypted path and use settings_path() instead

    • -19
    • +42
    /sources/device/DeviceController.cpp
I resolved my own message because of the conversation we had in terms of why I am making the change suggested.

I resolved my own message because of the conversation we had in terms of why I am making the change suggested.

I don't believe we need did * spaceChange. I am not interested in when the space changes. I am only interested when that partition gets too low on available space. Unless there is a case that you h...

I don't believe we need did * spaceChange. I am not interested in when the space changes.
I am only interested when that partition gets too low on available space. Unless there is a
case that you have which indicates otherwise.
This signal is similar to didSDCardSpaceTooLow, line 231

For SD card case, when the SD card is not ready, we update the visuals to set the "available" and "used" to 0 and emit the update. For this case, we are not updating any visuals. The need we have f...

For SD card case, when the SD card is not ready, we update the visuals to set the
"available" and "used" to 0 and emit the update. For this case, we are not updating
any visuals. The need we have for this function is to determine whether we are
low on available partition space and if we are, emit the "low" signal to handle