application

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Build failed on server because the fw common branch master was changed.

- commented out the removed enum from application.

    • -2
    • +2
    /sources/model/hd/alarm/MAlarmStatusData.cpp
Merge master into DEN-4860_BLE

    • -34
    • +36
    /sources/canbus/MessageInterpreter.cpp
    • -2
    • +6
    /sources/view/hd/alarm/VAlarmStatus.cpp
Merge branch 'DEN-5830_AlarmDesign'

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

    • -75
    • +57
    /sources/bluetooth/BLEScanner.cpp
    • -2
    • +2
    /sources/gui/qml/pages/SettingsBluetooth.qml
RESOLVED

RESOLVED

DEN-5753: Update Design Documents

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

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

I am not sure killing the QObject timer would be a good idea, but also I couldn't find any recommendation not to do it. Since any object has only one timer I have a feeling that by killing the obje...

I am not sure killing the QObject timer would be a good idea, but also I couldn't find any recommendation not to do it.
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.

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.

When we add the correct object dictionary in the names.py then sys/v&v/... can use it and don't need the object name anymore to do so. Not 100% agree. Also, we need to have a consistent naming for ...

When we add the correct object dictionary in the names.py then sys/v&v/... can use it and don't need the object name anymore to do so.
Not 100% agree.
Also, we need to have a consistent naming for the currently existing objectName in the code, I'll later provide a standard.

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

Please note that the code review has to be automatic, by making it manual and mixed up with other features, this may happen. RESOLVED

Please note that the code review has to be automatic, by making it manual and mixed up with other features, this may happen.
RESOLVED

RESOLVED

RESOLVED