| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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 is a very basic version of the clock used to make sure that
everything works, and I can manage to show the time on the display. No
button functions have been implemented yet. But, it works!
|
| |
|
