•  

Comment Results

Review Name Created Custom Fields Content
UI-DEN-4690-1 07 Oct 2020

added.
please refer to http://192.168.10.132:8060/cru/UI-DEN-4690-2-1#CFR-18381
line 44

UI-DEN-4690-1 07 Oct 2020

Added
http://192.168.10.132:8060/cru/UI-DEN-4690-2-1#CFR-18400
line 152

DIALIN-DEN-4690-1 07 Oct 2020

You're missing the return type

UI-DEN-4438-1 25 Aug 2020

"This is the namespace brace and the namespaces braces are not indenting the code. so are at the same column as class brace in this case."

UI-DEN-3605-4 30 Sep 2020

Move these definitions before // — PRS — section.
I also moved some of them in my code.

DG-DEN-5855-1 10 Dec 2020

RESOLVED in CODE WALKTHROUGH.

UI-DEN-4964-1 30 Oct 2020

RESOLVED

HD-DEN-4308-3 01 Sep 2020

Done

HD-DEN-9480-1 10 Nov 2021

Done.

DIALIN-DEN-4211-1 01 Sep 2020

RESOLVED

UI-DEN-3605-4 30 Sep 2020

Why the Slider.qml component has not been used?

HD-DEN-4308-3 02 Sep 2020

Removed fabs and I am using abs instead. I also removed all the absolute values that are not necessary.

UI-DEN-4964-1 30 Oct 2020

RESOLVED

HD-DEN-4308-3 02 Sep 2020

Fixed the algorithm.

DG-DEN-5855-1 10 Dec 2020

RESOLVED in CODE WALKTHROUGH.

HD-DEN-4211-1 14 Sep 2020

RESOLVED in CODE WALKTHROUGH.

DG-DEN-3504-1 07 Oct 2020

Target weight can be anything - comes from the HD. For calibration, I think we should be using a #define for what we think the fluid weight would be when reservoir drained to end of drain straw.

DG-DEN-3504-1 07 Oct 2020

Weight should be dropping. Probably shouldn't use fabs here.

UI-DEN-3605-4 05 Oct 2020

I removed all of these and just tested on the target and the performance appears to be the same.

The cpp code is in control of the business logic of when to enable/disable the continue button. Making the qml in control divides responsibility between the cpp code and qml as the cpp code needs to enable / disable it when we get a response back from FW.

The cpp code keeps track of which variable has been set and which hasn't.

Here are a couple of relevant requirements:

SRSUI 551: The "Continue" button shall be only enabled after all the "Treatment Parameters" has been set by user.
SRSUI 560: The "Create Treatment" screen shall display the "Treatment Parameters" values as has been set after user sets the value of each "Treatment Parameter".

UI-DEN-4690-1 16 Sep 2020

Although the comment is not relevant to the Story and to the code review, code comment has been removed regardless.

DIALIN-DEN-3421-1 14 Dec 2020

RESOLVED.

HD-DEN-5053-1 01 Oct 2020

Done.

UI-DEN-7044-1 07 Apr 2021

RESOLVED

HD-DEN-4308-3 22 Sep 2020

Done

UI-DEN-3605-4 30 Sep 2020

Please change Tr to Treatment.
It is not clear if used separately from the other ones.
The clear meaning is preferred.
Please align afterward.
Apply to all the others, please.

HD-DEN-4308-3 22 Sep 2020

Done

UI-DEN-4690-2-1 05 Oct 2020

This file and all the view file has been renamed to CamelCase but seems Crucible still insist to get a review on them.

HD-DEN-5053-1 22 Sep 2020

Done.

HD-DEN-5053-1 22 Sep 2020

Done.

UI-DEN-4690-2-1 05 Oct 2020

Good point, I don't know.
This is the way Crucible shows them.

HD-DEN-4308-3 23 Sep 2020

We thought about this. I think I would like to keep it this way to be more readable.

HD-DEN-5053-1 22 Sep 2020

Public was correct. Reverse the change.

HD-DEN-4308-3 23 Sep 2020

What about a get function for air trap valve?

HD-DEN-4308-3 22 Sep 2020

Should this only be incremented if major travel progress is not made? As it's coded, I think you're only giving the entire 1,000 step advancement 20 ms to complete.

HD-DEN-4308-3 23 Sep 2020

RESOLVED in CODE WALKTHROUGH.

UI-DEN-3605-4 07 Oct 2020

RESOLVED

UI-DEN-3605-4 05 Oct 2020

This has been deleted as it's not longer needed with an attached scrollbar

HD-DEN-4308-3 23 Sep 2020

RESOLVED in CODE WALKTHROUGH.

UI-DEN-3605-4 30 Sep 2020

What are these two extra object names?
If it's that much necessary can be moved inside the component implementation.
You have the object name and the postfix string is a constant string.

HD-DEN-4308-3 23 Sep 2020

RESOLVED in CODE WALKTHROUGH.

HD-DEN-4308-3 27 Aug 2020

This assumes we will be at position zero when we get here. Maybe true if first homing, but if we get here from idle, it may not be the case. I think you should set this target to current position + step change.

UI-DEN-3605-4 30 Sep 2020

Why this component is not in the code review?

HD-DEN-4308-3 05 Oct 2020

RESOLVED in CODE WALKTHROUGH.

UI-DEN-3605-4 08 Sep 2020

Please follow the code structure.

all the other cases are like each other and consistent why this implementation is different?

All :
vPayload = Format::fromVariant(vData);
LOG_EVENT(AdjustSalineRequestData::toString(vData));

This :
vPayload = Format::fromVariant(vData); // -------> Why data passed to this method instead of toString?
TreatmentParameters params;
params.fromVariantList(vData); // -------> why do you have this here?
LOG_EVENT("GOT HERE");
LOG_EVENT(params.toString()); // -------> same as first comment....

UI-DEN-4690-1 07 Oct 2020

RESOLVED

UI-DEN-3605-4 07 Oct 2020

I actually don't need it anymore, so it's deleted now. Will post the update soon

TESTSUITES-DEN-3724-1 07 Oct 2020

Why this is added?
The unit test for that feature was working and all the tests and coverage passed.
Why it has been modified?
Please remove it.

TESTSUITES-DEN-3724-1 07 Oct 2020

Why this is added?
The unit test for that feature was working and all the tests and coverage passed.
Why it has been modified?
Please remove it.

UI-DEN-3605-4 01 Sep 2020

RESOLVED.

UI-DEN-4438-1 25 Aug 2020

Absolutely,
I'm doing it incrementally and slowly to not to make the code reviews harder and confusing git.
I did for so many and this file will get its turn soon.