mirror of
https://github.com/ALLFATHER-BV/wadamesh.git
synced 2026-09-26 11:37:56 +00:00
Tesso M Costa
14d5fdb8b3
New Options > Lock screen toggle lets the at-a-glance overlay fire while the device is manually locked too, not just unlocked+idle-dimmed -- off by default since it makes message text readable off a locked device. Persisted via TouchPrefsStore (touchPrefsGetGlanceWhenLocked). When it fires from a locked state, mirrors lockscreenReveal()'s peek path (panel lit, _manual_lock left alone) rather than wakeScreen() (which would silently clear the lock). Also fixes the glance body label: LV_LABEL_LONG_DOT only wraps/dot- ellipsizes across multiple lines when the label has a fixed height, so left at auto-height it was effectively single-line everywhere, cropping longer messages instead of continuing to a second line. Now sized to the actual space available below it for the current board's resolution and font. Adds a T-Deck-only experiment shrinking the glance body font from 28px to 20px (extras_lat_20 gate widened past Tanmatsu-only to cover it); easy to revert in isolation per the comments at each site. Signed-off-by: Tesso M Costa <tesso.martins@gmail.com>
This directory is intended for project header files.
A header file is a file containing C declarations and macro definitions
to be shared between several project source files. You request the use of a
header file in your project source file (C, C++, etc) located in `src` folder
by including it, with the C preprocessing directive `#include'.
```src/main.c
#include "header.h"
int main (void)
{
...
}
```
Including a header file produces the same results as copying the header file
into each source file that needs it. Such copying would be time-consuming
and error-prone. With a header file, the related declarations appear
in only one place. If they need to be changed, they can be changed in one
place, and programs that include the header file will automatically use the
new version when next recompiled. The header file eliminates the labor of
finding and changing all the copies as well as the risk that a failure to
find one copy will result in inconsistencies within a program.
In C, the usual convention is to give header files names that end with `.h'.
It is most portable to use only letters, digits, dashes, and underscores in
header file names, and at most one dot.
Read more about using header files in official GCC documentation:
* Include Syntax
* Include Operation
* Once-Only Headers
* Computed Includes
https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html