aboutsummaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* Tweak gamma on ST7789 and match UI colorsRiku Isokoski2022-04-2529-88/+96
| | | | | This change will increase the color accuracy of the PineTime and make UI development with the simulator easier.
* Use centisecondsRiku Isokoski2022-04-251-4/+5
|
* Stopwatch fixesRiku Isokoski2022-04-252-37/+22
|
* Fix timer layoutRiku Isokoski2022-04-251-16/+11
|
* Firmware update screen fixesRiku Isokoski2022-04-251-11/+10
|
* SpiNorFlash: use C++ style struct in C++ only headerReinhold Gschweicher2022-04-241-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | `SpiNorFlash.h` is a C++ header, but the `Identification` struct is created in a C style using `typedef struct`. Clang issues a warining about this discrepancy: ``` In file included from /home/nero/repos/pinetime/InfiniSim/InfiniTime/src/systemtask/SystemTask.cpp:13: /home/nero/repos/pinetime/InfiniSim/sim/drivers/SpiNorFlash.h:16:21: warning: anonymous non-C-compatible type given name for linkage purposes by typedef declaration; add a tag name here [-Wnon-c-typedef-for-linkage] typedef struct __attribute__((packed)) { ^ Identification /home/nero/repos/pinetime/InfiniSim/sim/drivers/SpiNorFlash.h:17:9: note: type is not C-compatible due to this default member initializer uint8_t manufacturer = 0; ^~~~~~~~~~~~~~~~~~~~ /home/nero/repos/pinetime/InfiniSim/sim/drivers/SpiNorFlash.h:20:9: note: type is given name 'Identification' for linkage purposes by this typedef declaration } Identification; ^ 1 warning generated. ``` The easy fix is to use a C++ style struct. Also includes code style fix from Riksu9000 Co-authored-by: Riku Isokoski <riksu9000@gmail.com>
* Merge branch 'develop' into remove-nm-referenceMax Friedrich2022-04-1990-1072/+1584
|\
| * Replace lv_label_set_text where possibleRiku Isokoski2022-04-1822-104/+98
| |
| * Merge pull request #1009 from ↵Riku Isokoski2022-04-181-1/+2
| |\ | | | | | | | | | | | | NeroBurner/AlarmController_allow_less_precice_system_time AlarmController: allow loss of precision for alarmTime cast
| | * AlarmController: allow loss of precision for alarmTime castReinhold Gschweicher2022-03-291-1/+2
| | | | | | | | | | | | | | | Allow a loss of precision if the system clock has a lower resolution than nanoseconds. This is the case for web assembly.
| * | resolved merge conflict after renaming PineTimeStyle to WatchFacePineTimeStylemabuch2022-04-1829-175/+182
| |\ \
| | * | Let TouchHandler return TouchEvents instead of driver specific enumReinhold Gschweicher2022-04-134-33/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Let the TouchHandler::GestureGet() function return a TouchEvent instead of the touchpanel-driver specific enum. This helps to move the driver specific helper function `ConvertGesture` from `DisplayApp` into `TouchHandler`.
| | * | Replace airplane mode with a bluetooth toggleRiku Isokoski2022-04-0214-90/+72
| | |/
| | * Timer App : add background label to ensure that the app will be displayed ↵Jean-François Milants2022-03-283-20/+28
| | | | | | | | | | | | | | | | | | correctly after a full refresh (HW scrolling transition). Code cleaning and rename methods.
| | * DisplayApp : Call the event handler of the current app before loading the ↵Jean-François Milants2022-03-281-4/+4
| | | | | | | | | | | | new one. This way, we ensure that lv_task_handler() is called before sending event to the newly loaded app.
| | * New changes according to the review : Priority 0 for display, 1 for system, ↵Jean-François Milants2022-03-213-3/+4
| | | | | | | | | | | | timer and ble host, and 2 for ble LL
| | * Fix priorities of BLE tasksJean-François Milants2022-03-211-2/+2
| | |
| | * In current configuration, the timer task (the one from FreeRTOS) has the ↵Jean-François Milants2022-03-212-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | lowest priority (0). Both display and system tasks are also set on priority 0. In cases where any other task takes too much time to execute (it can happen in Display Task, see https://github.com/InfiniTimeOrg/InfiniTime/issues/825), the timer task does not have the opportunity to run fast enough to detect and debounce presses on the button. This commit sets the following priorities: - [0] : Display Task - [1] : Timer and System tasks - [2] : BLE Host - [3] : BLE LL This way, we ensure that button presses will always be detected, even if the rendering of the display takes a huge amount of time.
| | * Music app : when title/track name are truncated, add an ellipsis at the end ↵Jean-François Milants2022-03-211-5/+13
| | | | | | | | | | | | of the strings.
| | * Add missing space in if expression.Jean-François Milants2022-03-211-1/+1
| | |
| | * Limit the size of the track and album name received by MusicService. This ↵Jean-François Milants2022-03-211-0/+7
| | | | | | | | | | | | should work around this bug : https://github.com/InfiniTimeOrg/InfiniTime/issues/825 and prevent heap over-allocation.
| | * Merge pull request #1038 from NeroBurner/analog_local_variablesJF2022-03-142-13/+6
| | |\ | | | | | | | | WatchFaceAnalog: local date/time variables
| | | * WatchFaceAnalog: local date/time variablesReinhold Gschweicher2022-03-142-13/+6
| | | | | | | | | | | | | | | | Use local date and time variables. No need to store them in the object.
| | * | Merge pull request #1033 from NeroBurner/music_override_warningJF2022-03-141-1/+1
| | |\ \ | | | | | | | | | | Music: fix warning about overridden function
| | | * | Music: fix warning about overridden functionReinhold Gschweicher2022-03-131-1/+1
| | | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Clang warns on `OnTouchEvent()` function, which is overridden, but is missing the `override` keyword ``` In file included from InfiniTime/src/displayapp/screens/Music.cpp:18: InfiniTime/src/displayapp/screens/Music.h:43:14: warning: 'OnTouchEvent' overrides a member function but is not marked 'override' [-Winconsistent-missing-override] bool OnTouchEvent(TouchEvents event); ^ ```
| | * | Merge pull request #1034 from NeroBurner/twos_comparison_warningJF2022-03-141-1/+1
| | |\ \ | | | | | | | | | | Twos: fix warning about extra paranthesis
| | | * | Twos: fix warning about extra paranthesisReinhold Gschweicher2022-03-131-1/+1
| | | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We have a comparison like `if (( a == b ))`, which is a parenthesis too much, which generates the following warning ``` InfiniTime/src/displayapp/screens/Twos.cpp:133:35: warning: equality comparison with extraneous parentheses [-Wparentheses-equality] if ((grid[newRow][newCol].value == grid[oldRow][oldCol].value)) { ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ InfiniTime/src/displayapp/screens/Twos.cpp:133:35: note: remove extraneous parentheses around the comparison to silence this warning if ((grid[newRow][newCol].value == grid[oldRow][oldCol].value)) { ~ ^ ~ ```
| | * | WatchFaceAnalog: const ref to dateTimeControllerReinhold Gschweicher2022-03-141-1/+1
| | | | | | | | | | | | | | | | The clock app only reads from the dateTimeController, never modifies it.
| | * | DateTimeController: make possible functions constReinhold Gschweicher2022-03-142-4/+4
| | |/ | | | | | | | | | | | | MonthShortToString and DayOfWeekShortToString don't change the underlying object. Those are just getters and can be declared `const`.
| * / Rename PineTimeStyle to WatchFacePineTimeStylemabuch2022-03-125-22/+22
| |/
| * Merge pull request #1026 from NeroBurner/fix_settings_chimesJF2022-03-091-1/+1
| |\ | | | | | | Fix SettingChimes cbOption array size
| | * Fix SettingChimes cbOption array sizeReinhold Gschweicher2022-03-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | There are 3 options, but the array-size is set to 2. This leads to memory corruption in the initialization of the SettingChimes screen when assigning the third option object pointer. Found in https://github.com/InfiniTimeOrg/InfiniSim/issues/11
| * | Merge pull request #1005 from aveeryy/notifications-as-textJF2022-03-091-6/+6
| |\ \ | | |/ | |/| Terminal watchface: replace notifications icon with a text entry
| | * Remove unnecessary lineavery2022-03-061-1/+0
| | |
| | * Merge branch 'develop' into notifications-as-textavery2022-03-0612-48/+39
| | |\
| | * | Replace notif entry with "You have mail." textavery2022-03-051-6/+4
| | | |
| | * | terminal: Replace notification icon with a text entryavery2022-02-221-5/+6
| | | |
| | * | Use Bluetooth brand color for status textavery2022-02-221-4/+4
| | | |
| * | | Update navigation font readme sectionRiku Isokoski2022-03-082-11/+7
| | | |
| * | | Add ExtraBold font ttfRiku Isokoski2022-03-081-0/+0
| | | |
| * | | Further updates to font readme.Riku Isokoski2022-03-083-385/+416
| | | |
| * | | Update font readme, update fonts, add missing filesRiku Isokoski2022-03-087-238/+248
| | | |
| * | | SystemMonitor: implement FreeRtosMonitor only if trace facility is setReinhold Gschweicher2022-03-084-39/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Split SystemMonitor into h and cpp file and move the logging code of the `Process` function into the cpp file. Depending of the `configUSE_TRACE_FACILITY` define from `src/FreeRTOSConfig.h` create either a "FreeRtosMonitor" or a "DummyMonitor". Make the `Process()` function non-const, as the FreeRtosMonitor changes the member variable `lastTick`. In `SystemTask.h` we then only need to use `SystemMonitor`, without knowledge of the `configUSE_TRACE_FACILITY` define.
| * | | Add missing nrf_log.h includes shadowed by SystemMonitor.hReinhold Gschweicher2022-03-085-0/+5
| | |/ | |/| | | | | | | | | | | | | Some components were missing a `nrf_log.h` include. This missing include was accidentally provided by the SystemMonitor.h header, which was included by Systemtask.h
| * | removed SetClockFace from watchface ConstructorsYehoshua Pesach Wallach2022-03-032-2/+0
| | |
| * | Settings: more specific read and write modeReinhold Gschweicher2022-03-031-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | For each filesystem interaction be more specific if we want to read from the file or write to it. Doing a non-creating read on the loading of the settings file, otherwise an empty file could be created, and when reading that empty file for the initial settings I would expect an error (or random data) when reading.
| * | Update README.mdmedeyko2022-03-031-2/+1
| | | | | | | | | More imperative tone
| * | Update README.mdmedeyko2022-03-031-1/+1
| | | | | | | | | remove unnecessary )
| * | Update README.mdmedeyko2022-03-031-0/+17
| | |
| * | Update jetbrains_mono_bold_20.cmedeyko2022-03-031-2/+2
| | | | | | | | | Fix 0 (zero) symbol. For more details, #988