The approach comes from Qt's documentation: It's the QObjectList-based model approach https://doc.qt.io/qt-5/qtquick-modelviewsdata-cppmodels.html, which you can see creates a list of QObject* pointers with values that are accessible as named properties in the qml. This class has been tested and is working fine cppcheck doesn't report any errors in this file
Dara, rather than referring to another code review, I would just reply that it will be corrected after that code review is completed, branch merged to master, and then master pulled into this branch. Commenter can resolve then at that time when the fix shows up.
Persistent alarm now uses time interval limit rather than count. So we do not need to divide by the interval here. This change eliminates the need to know the task interval in which the checking function is getting called.
To avoid copying the has_value function into each enum sub-class, it'd be better to make AlarmUserOptions a subclass of DialinEnum, which can be imported from utils/base.py
You'll notice that the Qt company has only provided the button images in the svg format. It appears they did this to allow for greater customization of the keyboard styling in the qml code.
I'm aware it has been decided to use pngs in the denali application. If requested, I can change the default Qt-provided keyboard style.qml file to use pngs instead of svgs. It would be helpful before I do so to get feedback on the look and feel of the numeric keyboard so we have an agreed-upon style, size, and layout of the numeric keyboard, as converting the svgs to pngs will hard-code the styling.
The json document holds the information about the BP cuffs we've paired with. It is also helpful to format the paired device information into json so it can be stored to disk and then re-loaded easily so that we can automatically re-connect to the last selected BP cuff after a reboot. The dereferencing and casting is needed to work with the ObjectList-based model approach. All of the slots are there to receive data from the BLEScanner, so we can display available devices to connect to. We emit signals when we want to connect/reconnect to a device, scan for devices, or request to save the paired devices to disk.
You are running release
CR4.8.14
FE4.8.14
(20240111091859 2024-01-11 09:20),
please report your release number when reporting bugs.
