TDDefs.h

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDT-4013-1: Update fluid bolus enum and add tube set type enum

Yes, REmoved

Yes, REmoved

fixed

fixed

Added

Added

Removed

Removed

Added

Added

Fixed

Fixed

Fixed

Fixed

getNIBPControlStatus is a function, not a variable. Inputs should be "none". Fix these throughout this unit.

getNIBPControlStatus is a function, not a variable. Inputs should be "none". Fix these throughout this unit.

setNIBPCommand is a function, not a variable. I think Outputs should be "none"

setNIBPCommand is a function, not a variable. I think Outputs should be "none"

I think these fields are already U32s so no need to cast them.

I think these fields are already U32s so no need to cast them.

Initialize bpResults.

Initialize bpResults.

Add doxygen comment to right.

Add doxygen comment to right.

Remove extra blank line.

Remove extra blank line.

I think p comes before u. Move up one.

I think p comes before u. Move up one.

We should initialize BP module from main at startup so we can use it in any mode.

We should initialize BP module from main at startup so we can use it in any mode.

I think this should be executed from TaskGeneral so we can do BP things in any mode.

I think this should be executed from TaskGeneral so we can do BP things in any mode.

What is "e"? I think this might be a typo and you should put it back the way it was.

What is "e"? I think this might be a typo and you should put it back the way it was.

Fixed

Fixed

Fixed

Fixed

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

  1. … 2 more files in changeset.
LDT-4013: Merge latest staging into LDT-4013 and resolved merge conflicts

  1. … 2 more files in changeset.
Should this check be moved to the fluid bolus exec function?

Should this check be moved to the fluid bolus exec function?

It looks like you have this as a T/F response from UI. UI should not be determining whether the modality matches - that's our job. UI should be telling us which type of tubing set was installed (HD...

It looks like you have this as a T/F response from UI. UI should not be determining whether the modality matches - that's our job. UI should be telling us which type of tubing set was installed (HD or HDF type). Then when we get this response msg from UI, we will compare the type to the user selected modality (from TxParams) to see if it matches.

Add doxygen comments to the right of each structure field.

Add doxygen comments to the right of each structure field.