UI-DEN-6349

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

I have updated .gitignore so only bledevices.conf is ignored since it will be different for each device.

I have updated .gitignore so only bledevices.conf is ignored since it will be different for each device.

will be done later. RESOLVED

will be done later.
RESOLVED

needs to investigate more or done later. RESOLVED

needs to investigate more or done later.
RESOLVED

will be done later. RESOLVED

will be done later.
RESOLVED

will be done later. RESOLVED

will be done later.
RESOLVED

Resolved as per our code review 1.27.2021

Resolved as per our code review 1.27.2021

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

it may contain other settings so please don't ignore it in .gitignore.

it may contain other settings so please don't ignore it in .gitignore.

You asked for this change: We need to have a folder next to the application for all the settings since it is not related to the treatment it is only settings configuration files. Since the SD car...

You asked for this change:


We need to have a folder next to the application for all the settings since it is not related to the treatment it is only settings configuration files.
Since the SD card might be damaged and we still need to store settings.
Please change it to refer to the application location and name the folder as configuration or settings.


Here's a screenshot: X:\Users\PeterL\ForBehrouz\settings.png

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?