sources

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-6612 UI_DVT: Pre-Treatment Ultrafiltration

- This story wasn't part of the current sprint S37 but while I worked on it to be able to push it to master ASAP, so put the story as the commit comment.

  1. … 5 more files in changeset.
Why the doGetDevices is a public slots, therefore, is publicly accessible while you have a property defined for that? That's one of the reasons why I insisted to use macros to avoid this kind of in...

Why the doGetDevices is a public slots, therefore, is publicly accessible while you have a property defined for that?
That's one of the reasons why I insisted to use macros to avoid this kind of inconsistencies.
Also, the name of the property/signal/slot does not match.
if the property type is vTYPE and its name is vVARIABLE and the vSIGNAL is "Changed" then by PROPERTY macro definition it has to be like below with slot defined as private.

Q_PROPERTY(     vTYPE   vVARIABLE                                   \
                 READ   vVARIABLE                                   \
                 WRITE  vVARIABLE                                   \
                 NOTIFY vVARIABLE##vSIGNAL)                         \


The do/did/on prefixes will be used for none property matters.

what is this? why created and why ignored?

what is this?
why created and why ignored?

This is not a prefered approach and there are better ways of doing it. As Qt mentions in the document: QAbstractItemModel Subclass A model can be defined by subclassing QAbstractItemModel. This i...

This is not a prefered approach and there are better ways of doing it.
As Qt mentions in the document:


QAbstractItemModel Subclass
A model can be defined by subclassing QAbstractItemModel. This is the best approach if you have a more complex model that cannot be supported by the other approaches. A QAbstractItemModel can also automatically notify a QML view when the model data changes.

it has been done before please don't do this again RESOLVED

it has been done before please don't do this again
RESOLVED

RESOLVED

RESOLVED

DEN-5757: Code Coverage

Merge branch 'master' into DEN-5751_Pre-TreatmentUltrafiltration

  1. … 3 more files in changeset.
Server coverage issue fixed

- This line was not covered on server although it was covered on local.

Tested locally and it is working.

Build failed on server because the fw common branch master was changed.

- commented out the removed enum from application.

    • -4
    • +4
    ./view/hd/data/VHDTreatmentStatesData.cpp
Merge master into DEN-4860_BLE

    • -1
    • +1
    ./gui/qml/dialogs/NotificationDialog.qml
  1. … 5 more files in changeset.
Done

Done

DEN-4867: Code Review 0 - Requested Modifications

- Removed startBLETimer and killBLETimer so we are not creating and deleting timers. Only one timer will be used

- Added toggleBLETimer

- Logging measurements when they are received instead of using qDebug

- Passing device addr and name to BLEScanner instead of just addr so only a QBluetoothDeviceInfo object is necessary, allowing removal of the macAddress QString

- Removed VBluetoothDeviceInfo static cast in VBluetooth::doSelectDevice

  1. … 1 more file in changeset.
RESOLVED

RESOLVED

DEN-5753: Update Design Documents

- Fixed comments in some files of the Pre-Treatment Create.

  1. … 1 more file in changeset.
I will work on that later in prTx-UF story and it has only been fixed here since it wasn't passing the test sometimes while testing the Alarm design.

I will work on that later in prTx-UF story and it has only been fixed here since it wasn't passing the test sometimes while testing the Alarm design.

Yes I know. I accidently clicked it and there's no way to unclick

Yes I know. I accidently clicked it and there's no way to unclick

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

Our process calls for only 1 UNRESOLVED and 1 RESOLVED response (comment) per thread please.

Our process calls for only 1 UNRESOLVED and 1 RESOLVED response (comment) per thread please.

Much better, that should work. it's always a good practice to set the pointer to nullptr after delete, but since it is a local pointer that is fine. RESOLVED

Much better, that should work.
it's always a good practice to set the pointer to nullptr after delete, but since it is a local pointer that is fine.

RESOLVED

Fixed

Fixed

DEN-6359: Addressed code review comments

1 - I mean that timer is not only for handling our implementation it may have another purpose which we are stopping by killing the only timer it has. 2 - in your timerEvent { ... if( ! _tim...

1 - I mean that timer is not only for handling our implementation it may have another purpose which we are stopping by killing the only timer it has.
2 - in your

timerEvent {
    ...
    if( ! _timerIsActive ) return;
    ...
}
This is a leak/bug. Leak: A pointer to an object has been removed from the list and the object still exists and utilizing the memory (bug: and may even still doing some tasks).

This is a leak/bug.
Leak: A pointer to an object has been removed from the list and the object still exists and utilizing the memory (bug: and may even still doing some tasks).

Since any object has only one timer I have a feeling that by killing the object's only timer, then any refreshing or chores for any kind of signal/slot maintenance will be stoped. That's the inte...


Since any object has only one timer I have a feeling that by killing the object's only timer, then any refreshing or chores for any kind of signal/slot maintenance will be stoped.


That's the intention - to stop the timer. Since the UI is continually trying to reconnect to the last paired device while it is off, if a user goes into the bluetooth settings page and hits "Scan for devices", the timer is stopped during the scan to avoid conflicts between the timer and the scan.


I prefer to have a boolean flag to return from the virtual method in case we don't need it to handle the functionality we put there.


This doesn't make sense to me, can you clarify?

RESOLVED

RESOLVED

RESOLVED

RESOLVED