| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Prevents reading uninitialised memory if notification gets cut off due
to being more than 100 chars. The last character is assumed to be \0, but
it is actually uninitialised.
|
| | |
|
| | |
|
| |
|
|
| |
Also move one-line functions to header.
|
| |
|
|
| |
Could be used for other motion-based algorithms in the future.
|
| | |
|
| |
|
|
|
| |
These could be used for other motion-based algorithms in the future.
Also fix includes.
|
| | |
|
| |
|
|
| |
Fixes #1467 "Double tapping PineTimeStyle steps style button sends watch to sleep"
Double tap is disabled on the color settings screen by checking if the Rnd button is visible, but this didn't work for the options screen as the Rnd button isn't visible. I've changed it to check if the Close button is visible instead, which is used on both settings screens, and resolves the bug. I also changed the button used to disable the long press behaviour which was an as-yet-undiscovered bug which would have allowed the long press action to be used when the options screen was visible.
|
| |
|
|
| |
Define deepOrange color in InfiniTimeTheme
|
| |
|
|
| |
This reverts PR https://github.com/InfiniTimeOrg/InfiniTime/pull/1352
|
| | |
|
| |
|
|
|
|
|
| |
I don't think this badge has shown the actual status of the current
workflows for a long time. The real status can easily be seen by
clicking on the checkmark or cross icon on the front page. It's also
supposed to show the status of the master branch, not develop (default).
|
| |
|
|
|
|
| |
Previously, the LVGL driver for the filesystem was initialized in the class FS. However, since 6f942e2, the order of the initializations was incorrect : the driver was initialized (FS::LVGLFileSystemInit()) before LVGL (LittleVgl.Init()), which means that the driver registration was probably dropped when LVGL was initialized.
The LVGL driver is now initialized in LittleVgl.Init(), which seems to make much more sense, since all LVGL drivers are initialized there. This way, we ensure that the initialization of the drivers is consistent.
|
| |
|
|
| |
lv_color_hex can't be evaluated at compile time, but LV_COLOR_MAKE can.
|
| |
|
|
|
| |
This way warnings will be taken seriously, and will cause PR checks to
fail when they throw warnings.
|
| |
|
|
| |
Weather app is not fully implemented and is causing a warning
|
| |
|
|
| |
Fixes a compiler warning
|
| | |
|
| |
|
|
|
| |
This is a debugging app, not useful for most people.
Also remove the app icon.
|
| | |
|
| |
|
|
| |
DateTimeController can provide everything we need.
|
| | |
|
| |
|
|
|
|
| |
The systick doesn't need to be updated when setting time.
Also removed unused nrf_rtc.h includes.
|
| |
|
|
| |
SystemTask should never write to the lcd
|
| |
|
|
|
|
|
| |
LVGL is only a part of the main DisplayApp. Other "DisplayApps" can be
implemented without LVGL.
DummyLittleVgl isn't needed anymore and has been removed
|
| | |
|
| | |
|
| |
|
|
|
| |
This constructor didn't do anything since DisplayApp reference was
removed from the Screen base class.
|
| |
|
|
|
|
|
|
| |
The DisplayApp class isn't used in the Screen base class and most
screens, so requiring it is pointless.
In this commit, DisplayApp pointers were added to screens which use it
and the explicit Screen constructor was removed in those screens.
|
| | |
|
| |
|
|
|
| |
Vibrations should be associated with something happening on the UI.
Therefore SystemTask should not be controlling the motor.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Move LVGL specific code to the LittleVgl class
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This is so the GitHub UI picks it up correctly.
|
| |
|
|
| |
The GitHub UI doesn't resolve the link correctly
|
| | |
|
| |
|
|
|
| |
I find this format easier to read, because the definitions are at the
expected indentation, making it easier to find what I'm looking for.
|
| | |
|
| | |
|
| |
|
|
|
| |
These are instructions for maintainers, and should be in a separate
document.
|
| |
|
|
| |
Bigger buttons, use new color.
|
| |
|
|
|
|
| |
Long pressing will change the value by 1000, whereas clicks will change
it by 500. This allows setting more precise values, while also making it
easier to set any value.
|