TubeSetAutoEject.h

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Set "Stops" property back to TRUE like the other reserved UI alarms.

Set "Stops" property back to TRUE like the other reserved UI alarms.

break this line

break this line

add an empty else block after the last else if block in these functions handlePreTxHeparinPreloadState handlePreTxHeparinAwaitSyringeLoadConfirmationState handlePreTxHeparinSeekState handlePreTxHep...

add an empty else block after the last else if block in these functions
handlePreTxHeparinPreloadState
handlePreTxHeparinAwaitSyringeLoadConfirmationState
handlePreTxHeparinSeekState
handlePreTxHeparinPrimeState
handlePreTxHeparinBolusState

break this line

break this line

Add initialization for heparinSetupResumeRequested and syringeLoadConfirmed

Add initialization for heparinSetupResumeRequested and syringeLoadConfirmed

Align all the function comments

Align all the function comments

Delete this row.

Delete this row.

Should this be the "Load Syringe" alarm that you just added?

Should this be the "Load Syringe" alarm that you just added?

I think ( setTxDur - preStop ) should be changed to ( preStop ). Also, I think preStop should be renamed to hepDurMin.

I think ( setTxDur - preStop ) should be changed to ( preStop ).
Also, I think preStop should be renamed to hepDurMin.

Can we remote this TODO comment?

Can we remote this TODO comment?

Remove blank line.

Remove blank line.

We should go to dry self test state. Why did this change to Rx state?

We should go to dry self test state. Why did this change to Rx state?

Comment - should be "install" not "instll".

Comment - should be "install" not "instll".

I don't see any change here. How does this function get called? I don't see the function being used anywhere - nobody is calling it. I think it should be called by Messaging.c when a UI confirmatio...

I don't see any change here. How does this function get called? I don't see the function being used anywhere - nobody is calling it. I think it should be called by Messaging.c when a UI confirmation msg is received.

171

171

Who is calling this function? Should be coming from UI, right? So should be a message handler (returns BOOL, takes a message as param, function is in table at top of Messaging.c).

Who is calling this function? Should be coming from UI, right? So should be a message handler (returns BOOL, takes a message as param, function is in table at top of Messaging.c).

Need to set state to preload state I think. Otherwise you will go to interrupted state.

Need to set state to preload state I think. Otherwise you will go to interrupted state.

Why did you remote call to init function here? Is it initialized somewhere else?

Why did you remote call to init function here? Is it initialized somewhere else?

Use ternary operation to assign TRUE or FALSE explicitly.

Use ternary operation to assign TRUE or FALSE explicitly.

This is at end of enum list above. So it should be at end of table here.

This is at end of enum list above. So it should be at end of table here.

What alarm is this? It doesn't look like you've added a new alarm. This is one of the reserved (unused) alarms that UI s/w might use.

What alarm is this? It doesn't look like you've added a new alarm. This is one of the reserved (unused) alarms that UI s/w might use.

Do we really need these setup functions for each state? They all look very simple - just 1 or 2 lines of code.

Do we really need these setup functions for each state? They all look very simple - just 1 or 2 lines of code.

I believe the SyringePump controller will trigger this alarm at end of seek operation.

I believe the SyringePump controller will trigger this alarm at end of seek operation.

Syringe pump should already be stopped if preload is done. Do we need to call this here?

Syringe pump should already be stopped if preload is done. Do we need to call this here?

This is called from preload state. Not needed here I think.

This is called from preload state. Not needed here I think.

Don't put comments on function prototypes. Doxygen gets details of functions from the function header.

Don't put comments on function prototypes. Doxygen gets details of functions from the function header.

Why (void)?

Why (void)?

Where is this being called? Should be called from pre-treatment init I think.

Where is this being called? Should be called from pre-treatment init I think.

Why are we signaling syringe load confirmed here?

Why are we signaling syringe load confirmed here?

Do these states need to be public?

Do these states need to be public?