HDDefs.h

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
HD-DENBUG-328_Venous Pressure Alarm Did Not Trigger When Pressure Dropped TO 0 Mmhg Stagi
HD-DENBUG-328_Venous Pressure Alarm Did Not Trigger When Pressure Dropped TO 0 Mmhg Stagi
Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

  1. … 1 more file in changeset.
DENBUG-328 added an air trap event

HD-DENBUG-328_Venous Pressure Alarm Did Not Trigger When Pressure Dropped TO 0 Mmhg Staging
HD-DENBUG-328_Venous Pressure Alarm Did Not Trigger When Pressure Dropped TO 0 Mmhg Staging
DG-DENBUG-298_User Unable TO Deliver Saline P1B Staging
DG-DENBUG-298_User Unable TO Deliver Saline P1B Staging
Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

  1. … 3 more files in changeset.
RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Done

Done

Bad practice to have two calls to same function here. Possible that 2nd call will return different result. Should call function once to assign value to a local var prior to if statement and then re...

Bad practice to have two calls to same function here. Possible that 2nd call will return different result.
Should call function once to assign value to a local var prior to if statement and then reference the local var in the if statement.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Yes. I think we should have these events to information.

Yes. I think we should have these events to information.

Are these permanent?

Are these permanent?

DENBUG-302 added UF rate events for information

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Add comment explaining what we're doing here.

Add comment explaining what we're doing here.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Moved it to OperationModes

Moved it to OperationModes

For other confirmations, an executive (e.g. alarm mgmt monitor or standby mode exec) is responsible for checking confirmation status and we don't call specific handlers from here. Why can't we foll...

For other confirmations, an executive (e.g. alarm mgmt monitor or standby mode exec) is responsible for checking confirmation status and we don't call specific handlers from here. Why can't we follow that design pattern for this confirmation?

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Done

Done