| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
This allows to "debloat" the space for others apps, which are not
always loaded in memory, unlike home_menu.
|
| |
|
| |
|
| |
|
|
|
|
| |
This should probably be moved to a textfile in a doc directory.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This should help remedy malloc (and new) failures. This is (naturaly) not
a replacement for checking if malloc/new has failed!
|
| |
|
|
|
|
| |
This might help in debugging problems related to memory and malloc-ing.
|
|\
| |
| |
| | |
Add a few new API features.
|
| | |
|
| |
| |
| |
| | |
This allows creating a menu with more ease.
|
| |
| |
| |
| | |
choosing number
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This allows implementing different popup types with more ease.
This new function made me notice that the application's heap (and maybe
stack) usage is high. When testing the updated gui_popup_text method, I
noticed that sometimes, the std::string cannot be allocated.
There are more details in the updated api header file.
|
| |
| |
| |
| |
| | |
This reduces display flickering and might help in having a longer
battery life.
|
|/ |
|
|
|
|
| |
Current app stops getting refreshed and display is turned off.
|
| |
|
|\ |
|
| |
| |
| |
| | |
Possible fix
|
| | |
|
| |
| |
| |
| |
| | |
This is to lower power consumption by having the apps set the lowest
performance they need.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
I had to modify the OLED library to correctly work with newlines.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
When the value references an out of bounds memory address, line 47 in
same file may cause hardfault/segmentation fault.
|
|/
|
|
|
|
|
|
|
|
|
| |
It is currently very basic as functions will be added to it when the time
comes. The idea is to have a method to, for example, show notifications
(and store them in a list with metadata) to the user or also to easily
show a message box overlaying the current display.
Private class members will permit encapsulations of variables related
to these features and limit the privilage that each app has on the
device.
|
|
|
|
|
|
|
| |
Stop using APPS_DATA. Dynamic allocation allows to avoid having memory
used by unloaded apps, thus giving more memory to running apps. Make
sure to correctly deallocate with `delete` to avoid memory leaks!
Exceptions to allocate memory will have to be handled...
|
|
|
|
|
|
| |
It is generally misleading as header files are marked as unresolvable
when it is not the case. I also tried to fix the problem by adjusting
where libraries are searched by Intellisense.
|
| |
|
|
|
|
|
|
|
|
| |
A large number of changes had to be made to use C++. "extern C" had to
be added for a few headers not adapted to C++. See
https://github.com/raspberrypi/pico-sdk/pull/106 for fix in affected
files. They will be removed when the pull request is merged in
pico-sdk's master branch.
|
|
|
|
|
|
|
|
|
| |
Buttons are now detected and reported to the current running application
(demoed in main_clock and home_menu with `oledWriteString(oled, 0,0,2,
&data[0], FONT_6x8, 0, 1);`). I start to see the limitations with
APP_DATA. It will be dropped in a futur commit after moving each app
into its own namespace. Variables will be allocated dynamically on app
init.
|
|
|
|
|
| |
I did changes to apps/main_clock as this app is also used for testing new
features.
|
| |
|
|
|
|
|
| |
Each app has its own init, render, bgrefresh and destroy functions.
The app data array alllows apps to persist data between function calls.
|
| |
|
|
|
|
|
| |
This simplfies setting the display contrast. A low value is used to save
a little power and also to have the OLED last a bit longer.
|