en_US.dic

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
RESOLVED. My understanding is that this will be connected in a future story

RESOLVED.
My understanding is that this will be connected in a future story

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

Done

Done

Removed.

Removed.

Is there a reason these shouldn't be deleted?

Is there a reason these shouldn't be deleted?

RESOLVED.

RESOLVED.

To make it consistent these could also be red and white without double quotes

To make it consistent these could also be red and white without double quotes

done

done

Thanks for reminding that. updated all the other ones as well. done.

Thanks for reminding that.
updated all the other ones as well.
done.

Great question. There would be another connection for the message "Treatment Parameters validation" and that will update the properties here when that message with parameters received. It would be ...

Great question.
There would be another connection for the message "Treatment Parameters validation" and that will update the properties here when that message with parameters received.
It would be an extra :
ACTION_VIEW_CONNECTION(AdjustPressuresLimitsResponseData);
with the correct model as a parameter and another:
void VTreatmentAdjustmentPressuresLimits::onActionReceive(const AdjustPressuresLimitsResponseData &vData)
with that model as parameter.

The message ID is in decimal not hex

The message ID is in decimal not hex

Once the user has selected the arterial and venous pressure limits in pre-treatment, before they try to adjust them, how are the values they chose in pre-treatment displayed here?

Once the user has selected the arterial and venous pressure limits in pre-treatment, before they try to adjust them, how are the values they chose in pre-treatment displayed here?

Remove extra line.

Remove extra line.

UI-DEN-4691_Inline Blood Pressure Adjustments
UI-DEN-4691_Inline Blood Pressure Adjustments
RESOLVED

RESOLVED

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

Objectives: #01 Because of the new standard message (#01) I could be able to use the FW's returned reason filed for the new message which the old one didn't have. So removed UI handling of the mess...

Objectives: #01
Because of the new standard message (#01) I could be able to use the FW's returned reason filed for the new message which the old one didn't have.
So removed UI handling of the message rejection reason by the FW one as designed by standard Response messages.

Objectives: #01, #04 Because of the new standard message (#01) I could be able to use my notify template function (#04) and then these codes are not used anymore.

Objectives: #01, #04
Because of the new standard message (#01) I could be able to use my notify template function (#04) and then these codes are not used anymore.

Objective: #14 This is the dictionary file for the QtCreator spellcheck plugin.

Objective: #14
This is the dictionary file for the QtCreator spellcheck plugin.