canbus

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
This needs to be updated to 10 * 4 if the change to the "TreatmentStates" is approved by Sean Nash. Also please remove the duplicate.

This needs to be updated to 10 * 4 if the change to the "TreatmentStates" is approved by Sean Nash.
Also please remove the duplicate.

Sean Nash, How the change to the TreatmentState message will affect the Application? This newly added parameter seems redundant to me. The change is the "Dialysis State" addition. 10 - (U32) Dial...

Sean Nash,
How the change to the TreatmentState message will affect the Application?
This newly added parameter seems redundant to me.

The change is the "Dialysis State" addition.

10 - (U32) Dialysis state
Unknown macro: { 0=start, 1=UF, 2=saline bolus }

0x0F00 15 0x040 4 Hz N HD All Treatment State sub-mode (U32-enum) (U32) UF state (U32) saline bolus state (U32) Hep state (U32) Rinseback state (U32) Recirc state 7 - (U32) Bld Prime state 8 - (U32) Tx End state 9 - (U32) Stop state 10 - (U32) Dialysis state
Please remove the box column, we decided not to use it in the Application documentation. Please do this for all the new models added.

Please remove the box column, we decided not to use it in the Application documentation.
Please do this for all the new models added.

It has been defined in the AlarmItem. Expose the VAlarmStatus property from AlarmItem.qml by adding this line: readonly property alias alarm_AlarmID : vAlarmStatus.alarm_AlarmID then use the ...

It has been defined in the AlarmItem.
Expose the VAlarmStatus property from AlarmItem.qml by adding this line:

    readonly property alias alarm_AlarmID : vAlarmStatus.alarm_AlarmID


then use the AlarmItem object, (which has been defined in the main.qml) to get the alarm id like the line below:

_alarmItem.alarm_AlarmID


Thanks,

Users can not see the alarm screen when the diagnostics screen is visible. This was a request by systems in DEN-12118. Is there another approach to this?

Users can not see the alarm screen when the diagnostics screen is visible. This was a request by systems in DEN-12118. Is there another approach to this?

it has already been defined, this would be a duplicate handler. why do we need to have the top on diagnostics while it has to always be on alarm dialog/bar on screen?

it has already been defined, this would be a duplicate handler.
why do we need to have the top on diagnostics while it has to always be on alarm dialog/bar on screen?

Required to display the Alarm Top on the diagnostic screen

Required to display the Alarm Top on the diagnostic screen

keep one line empty on top of the // HD Data Messages

keep one line empty on top of the // HD Data Messages

Why VAlarmStatus is added?

Why VAlarmStatus is added?

This message has been defined with 5xF32 parameters. 0x3100 49 0x080 1 Hz N DG All DG Conductivity Data (F32) RO rejection ratio (F32) CPi conductivity (F32) CPo conductivity (F32) CD1 conductivit...

This message has been defined with 5xF32 parameters.

0x3100 49 0x080 1 Hz N DG All DG Conductivity Data (F32) RO rejection ratio (F32) CPi conductivity (F32) CPo conductivity (F32) CD1 conductivity (F32) CD2 conductivity
UI-DEN-12121_SW Dev Sprint 65
UI-DEN-12121_SW Dev Sprint 65
RESOLVED.

RESOLVED.

Actually, this is correct. And it should not have parenthesis like you said, otherwise it becomes incorrect. if I write it like : ( ( x * ( maximum - minimum ) ) / width ) + minimum then too man...

Actually, this is correct.
And it should not have parenthesis like you said, otherwise it becomes incorrect.
if I write it like :

 ( ( x * ( maximum - minimum ) ) / width ) + minimum 

then too many /redundant parentheses make it confusing.

To make sure the addition is done first, should you put ( width + minimum ) ?

To make sure the addition is done first, should you put ( width + minimum ) ?

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

Thanks, Updated.

Thanks,
Updated.

Thanks, Aligned.

Thanks,
Aligned.

This is part of an ongoing investigation on how to fix the slider touch margin issue. I am still working on it. It worked somehow for the slider with lower resolution but for sliders, with a high r...

This is part of an ongoing investigation on how to fix the slider touch margin issue.
I am still working on it.
It worked somehow for the slider with lower resolution but for sliders, with a high resolution, it causes a handler jump which makes it less user-friendly.
Added clarifying comment.

This is the Trends screen. It is needed since it has not been implemented yet has been commented out.

This is the Trends screen.
It is needed since it has not been implemented yet has been commented out.

If not needed, why not just delete this line?

If not needed, why not just delete this line?

Why commented out?

Why commented out?

Lines above are formatted to align terms of equation. This line is not.

Lines above are formatted to align terms of equation. This line is not.

Thickness?

Thickness?

UI-BUG-S63
UI-BUG-S63