application

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-7147: Code Review 0

- DEN-7823: Meetings & Support - General Purpose - Kushen Pre-Treatment Images.

    • binary
    /resources/settings/instructions/slide1_filter_v2.png
    • binary
    /resources/settings/instructions/slide1_filter_v2b.png
RESOLVED

RESOLVED

Thanks. Are we going to need to review your merge commits as well?

Thanks. Are we going to need to review your merge commits as well?

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

it is an alias name for ISO/IEC_8859-1 character encoding standard. https://en.wikipedia.org/wiki/ISO/IEC_8859-1

it is an alias name for ISO/IEC_8859-1 character encoding standard.
https://en.wikipedia.org/wiki/ISO/IEC_8859-1

Why Latin1 and not Latin? Are there two or more Latins?

Why Latin1 and not Latin? Are there two or more Latins?

DEN-7521: Ensure static IP assignments display after reboot

Will '[' and ']' always be on the same line?

Will '[' and ']' always be on the same line?

Can this be deleted?

Can this be deleted?

Don't think prepend("/") is needed here since according to https://doc.qt.io/qt-5/qfileinfo.html#absolutePath, "On Unix the absolute path will always begin with the root, '/', directory."

Don't think prepend("/") is needed here since according to https://doc.qt.io/qt-5/qfileinfo.html#absolutePath, "On Unix the absolute path will always begin with the root, '/', directory."

If '=' is the last character or first character in the line this won't work

If '=' is the last character or first character in the line this won't work

This function only returns 0 so it can be void

This function only returns 0 so it can be void

Is there protection in case the file is being written to while you are trying to read it? Doesn't QSettings do all of this for us already?

Is there protection in case the file is being written to while you are trying to read it? Doesn't QSettings do all of this for us already?

Is this needed or can it be deleted?

Is this needed or can it be deleted?

I see, could you update the comment to say "other than only just logging" so it's clearer? I was totally confused by it

I see, could you update the comment to say "other than only just logging" so it's clearer? I was totally confused by it

These are test files for now. Later when we have a real file designed these will be replaced with some real names.

These are test files for now.
Later when we have a real file designed these will be replaced with some real names.

Is this class really needed? QSettings is already thread-safe. What does this class do that QSettings doesn't already do?

Is this class really needed? QSettings is already thread-safe. What does this class do that QSettings doesn't already do?

Docstrings are missing in this class

Docstrings are missing in this class

vGroup is being used so I think you can remove Q_UNUSED

vGroup is being used so I think you can remove Q_UNUSED

Thanks for reminding me that, Yes I saw that. I Will taking care of it.

Thanks for reminding me that, Yes I saw that.
I Will taking care of it.

I was trying to say the sorting may require to change later because the birthTime is not returning a valid date. And maybe sorting on the name which always returns a valid value is better. Also has...

I was trying to say the sorting may require to change later because the birthTime is not returning a valid date.
And maybe sorting on the name which always returns a valid value is better.
Also has a note that if it is going to change, be careful that it is going to use for different purposes other than only logging.

I added these already to staging, but they are named BUILD_FOR_DESKTOP and BUILD_FOR_TARGET. So when you merge staging to your branch or vice versa be sure to rename all of mine or make sure all of...

I added these already to staging, but they are named BUILD_FOR_DESKTOP and BUILD_FOR_TARGET. So when you merge staging to your branch or vice versa be sure to rename all of mine or make sure all of them are named the same since there's no need for duplicates. Also, are we still going to review merges as I don't think there is a merge commit yet from staging to this branch in this code review.

RESOLVED

RESOLVED

Not sure I follow the comment you added here, can you clarify?

Not sure I follow the comment you added here, can you clarify?

This image filename could be more descriptive. Will it have to be renamed if the order is changed?

This image filename could be more descriptive. Will it have to be renamed if the order is changed?

DEN-7832: Implementations [Saline and Heparin change request]

- Reverted back the ultrafiltration state removal. The UF requires the state in the response message since we don't have any specific ultrafiltration adjustment state message .

    • -1
    • +33
    /sources/view/hd/data/VHDTreatmentStatesData.cpp
It's working on the Sprint37 branch of the Common. FW hasn't updated on the master yet.

It's working on the Sprint37 branch of the Common.
FW hasn't updated on the master yet.

DEN-7832 Implementations [Saline and Heparin change request]

- updated the messages length

- disabled used on heparin complete state to resume the heparin

- fixed the issue caused the entire section stay touchable and send the request on saline and heparin.

- updated the wording of the heparin state messages.

- added a define to disable the UI Check-In

When I tried to test out your branch, I got a compilation error saying that DRY_SELF_TESTS_SYRINGE_PUMP_PRIME_STATE doesn't currently exist in HDDefs.h. My common has the latest changes

When I tried to test out your branch, I got a compilation error saying that DRY_SELF_TESTS_SYRINGE_PUMP_PRIME_STATE doesn't currently exist in HDDefs.h. My common has the latest changes