FrameInterface.cpp

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
RESOLVED

RESOLVED

RESOLVED

RESOLVED

fixed, thanks!

fixed, thanks!

this looks like this will error.. Should be     title: qsTr("Treatment Delivery & Blood Handling")

this looks like this will error.. Should be

    title: qsTr("Treatment Delivery & Blood Handling")
RESOLVED

RESOLVED

Understood, will consider in a future story to adjust all models

Understood, will consider in a future story to adjust all models

addressed

addressed

For the models, in their infoText functions, use QStringLiteral when generating the string that is getting returned, if possible. (https://doc.qt.io/archives/qt-5.15/qstring.html#QStringLiteral)

For the models, in their infoText functions, use QStringLiteral when generating the string that is getting returned, if possible.
(https://doc.qt.io/archives/qt-5.15/qstring.html#QStringLiteral)

probably do not need to translate because its a diagnostics page but to keep consistent with all other user facing texts in this file please translate.

probably do not need to translate because its a diagnostics page but to keep consistent with all other user facing texts in this file please translate.

LDT-931: Main Treatment Screen - SW - Diagnostics Screen-FP - 05: DEV - Feature Implementation

- Add FP Folder structure

- Add The following FP message implementation

Versions

Pressure

Flow

Conductivity

Temperature

Valves

ROPump

BoostPump

Level

-Add FP can channel to Can interpreter

-Implement FP diagnostics screen

  1. … 49 more files in changeset.
LEAHI-APPLICATION-LDT-926_Feature/Ldt 926 Main Treatment Screen SW 01 Diagnostics Screen FP
LEAHI-APPLICATION-LDT-926_Feature/Ldt 926 Main Treatment Screen SW 01 Diagnostics Screen FP
RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

This code is still in the early stage of development, and the debug codes are helpful to keep.

This code is still in the early stage of development, and the debug codes are helpful to keep.

To ensure that specific components are not referenced anywhere, I do not assign an ID to them. As for the name, however, we'll ensure that it is only added if it needs to be included in the SquishQ...

To ensure that specific components are not referenced anywhere, I do not assign an ID to them.
As for the name, however, we'll ensure that it is only added if it needs to be included in the SquishQt integration test.

This type of spacing is used in the SW/UI to facilitate the use of vertical selection and vertical alignment.

This type of spacing is used in the SW/UI to facilitate the use of vertical selection and vertical alignment.

To make the ! more visible, I always try to put a space between the ! and the surrounding text (not to be confused or misread with i,l,|).

To make the ! more visible, I always try to put a space between the ! and the surrounding text (not to be confused or misread with i,l,|).

missing id and object name properties

missing id and object name properties

remove space after '!'

remove space after '!'

remove commented out line?

remove commented out line?

remove spacing after vAdjustmentVersions.. same goes for the other times vAdjustmentVersions is being called in this file

remove spacing after vAdjustmentVersions.. same goes for the other times vAdjustmentVersions is being called in this file