twislaandClaude Opus 5.5
7fe8b3d22a
Fn+h on any screen, text fields included, and ? outside Text Entry, open a panel over the content area: the screen's own keys, then the ones that work everywhere. Every App declares its keys for the state it is in (pages, viewers, dialogs and text fields answer for themselves); the App manager opens the panel and takes every key while it is open. About 30 hint lines are gone, from every App. What stays on a screen is state. The first-start Setup keeps its hints and teaches the key; a device set up before gets one Toast, once. The guide and the FAQ open with it. `key help` over the consoles. 476 host tests (8 new). Checked on the device with key help and screenshots: the Launcher, all nine Apps and several of their states. 8.5 KB of flash and 40 bytes of static RAM. Decisions Q196 to Q203 in docs/milestones/U1.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT
1.0 KiB
+++ title = "User guide" description = "How to use each App on the Cardputer: the keys, what the screens show, and what is written to the SD card." template = "guide-index.html" sort_by = "weight" page_template = "guide-page.html" +++
This guide says what the firmware does today and nothing else. Start with the basics (the keys, the Launcher, the first start), then read the page of any App. On the device itself, Fn + h lists the keys of whatever screen you are on: nothing else on a screen names them. It describes the latest release; the numbers and key names come from the firmware's own source.
The mesh messenger is planned, not built. The LoRa Scanner listens to Meshtastic traffic and shows it, but the device sends nothing yet: that is the next milestone and waits for a second node to test with.
Looking for a recipe or a quick answer? There are how-tos and a FAQ.
Something missing or wrong? Write to the issue tracker or to contact@roro9stack.net.