| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
status_check and cb_status_check.
|
|
|
|
|
| |
The main loop was reordered for a little optimisation as we cannot set
free standingly(?) anymore the render interval to 0.
|
|
|
|
|
|
|
|
|
| |
This simplifies managing the change of foreground app. Use the
performance_render_interval_{set,get} functions would be too cumbersome
to implement. Unfortunately, this might give too much freedom to running
apps, as they can decide to use a very small render interval which can
use more battery as the system cannot sleep while waiting for the next
render cycle.
|
|
|
|
|
| |
This is a more descriptive name as there could be multiple apps that are
currently open, or on-screen, such as a system UI or a status bar.
|
|
|
|
| |
This helps with compartmentalisation and organisation.
|
| |
|
|
|
|
|
|
|
|
|
| |
and create classes for home_menu and main_clock apps.
This commit has a lot of changes as multiple parts of the project had to be
changed to support running apps that are based on the BaseApp class. It
could not have been done in multiple commits as the progam would not be
able to build and thus I would not be able to test the changes.
|
|
|
|
| |
They have been moved to a new file, to provide better encapulation.
|
|
|
|
|
|
|
|
| |
It is derived by each app. This allows finally allocating space for an
app's variable when it is opened.
On the other hand, currently, destruction of apps is not fully
implemented. This commit is also done to save a snapshot of something that
works.
|
| |
|
| |
|
|
|
|
| |
This allows add to implement double clicking, for instance.
|
|
|
|
|
| |
This allows later updating the code to have the check work correctly
when start time > current time.
|
|
|
|
|
|
|
|
|
| |
This existed because waiting for the app to finish rendering was done in
a blocking manner, meaning that the rendering state would never end.
This would block the microcontroller in a loop.
This was fixed by rewriting the part related to app switching to
correctly do the switching while the app is not rendering.
|
| |
|
|
|
|
|
|
|
| |
This avoids quitting the app when an Api popup is displayed, causing
problems.
The variable resposable for this has been renamed to better reflect its
use.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This might help in debugging problems related to memory and malloc-ing.
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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...
|
| |
|
|
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.
|