Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
When will commented code be removed.

When will commented code be removed.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

converted all calls to setCurrentSubState to have a casted U32. Thanks!

converted all calls to setCurrentSubState to have a casted U32. Thanks!

Fixed. Thanks!

Fixed. Thanks!

My mistake. fixed!

My mistake. fixed!

My mistake. fixed!

My mistake. fixed!

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Done

Done

Done

Done

HD-DIAL-252_Request Create Dialin Command TO Enable Air Bubble Alarm IN Service Mode Air Bubble
HD-DIAL-252_Request Create Dialin Command TO Enable Air Bubble Alarm IN Service Mode Air Bubble
Correct, no longer required. Removed.

Correct, no longer required. Removed.

Reset proper flag.

Reset proper flag.

We are (I think now) allowing door open in first 2 states (UF and invert dialyzer), so should not be getting door open alarm when UI is prompting user to invert dialyzer. When we get to 3rd state (...

We are (I think now) allowing door open in first 2 states (UF and invert dialyzer), so should not be getting door open alarm when UI is prompting user to invert dialyzer. When we get to 3rd state (where we start requiring door to be closed), we are looking for user to connect patient and confirm. UI should be following along with our states and showing appropriate screens.
RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Doesn't look removed. I'm talking about the call to handlePatientConnectionDoorOpened(). Do we need this now that door closed is required (as set in prior state)?

Doesn't look removed. I'm talking about the call to handlePatientConnectionDoorOpened(). Do we need this now that door closed is required (as set in prior state)?

Doesn't make sense to reset in previous state. You're resetting door opened flag there. I'm talking about patient connect confirm flag used in if statement above.

Doesn't make sense to reset in previous state. You're resetting door opened flag there. I'm talking about patient connect confirm flag used in if statement above.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.