mirror of
https://github.com/MarekZegare4/MeshCore-Solo.git
synced 2026-07-26 14:58:12 +00:00
deploy: 866e44c4e2
This commit is contained in:
File diff suppressed because one or more lines are too long
44
sitemap.xml
44
sitemap.xml
@@ -2,90 +2,90 @@
|
||||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/cli_commands/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/companion_protocol/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/docs/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/faq/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/kiss_modem_protocol/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/nrf52_power_management/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/number_allocations/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/packet_format/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/payloads/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/qr_codes/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/stats_binary_frames/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/terminal_chat_cli/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/design/nearby_redesign/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/design/solo_ui_framework/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/design/trail_redesign/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/solo_features/clock_screen/clock_screen/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/solo_features/favourites_dial/favourites_dial/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/solo_features/message_screen/message_screen/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/solo_features/screen_lock/screen_lock/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/solo_features/settings_screen/settings_screen/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/solo_features/tools_screen/tools_screen/</loc>
|
||||
<lastmod>2026-07-05</lastmod>
|
||||
<lastmod>2026-07-06</lastmod>
|
||||
</url>
|
||||
</urlset>
|
||||
BIN
sitemap.xml.gz
BIN
sitemap.xml.gz
Binary file not shown.
@@ -1738,7 +1738,7 @@
|
||||
<p><strong>Hold Enter</strong> (or press the <strong>Context menu</strong> key) on the Clock page to open the Dashboard Config screen, where each of the three field slots can be cycled with <strong>LEFT/RIGHT</strong>.</p>
|
||||
<hr />
|
||||
<h3 id="clock-tools-alarm-timer-stopwatch">Clock tools — Alarm, Timer, Stopwatch</h3>
|
||||
<p><strong>Press Enter</strong> (short press) on the Clock page to open <strong>Clock Tools</strong>, a small menu with three time utilities. <strong>Cancel</strong> backs out one level (tool → menu → home).</p>
|
||||
<p><strong>Press Enter</strong> (short press) on the Clock page to open <strong>Clock Tools</strong>, a small menu with three time utilities. <strong>Cancel</strong> backs out one level (tool → menu → home). The same menu also has an entry under <strong>Tools › System</strong>, so it's reachable without the Clock page.</p>
|
||||
<h4 id="alarm">Alarm</h4>
|
||||
<p>A single one-shot wake alarm. Rows: <strong>Hour</strong>, <strong>Minute</strong> and <strong>Armed</strong>. <strong>Enter</strong> on Hour or Minute opens the digit editor (LEFT/RIGHT moves between the tens/units, UP/DOWN changes the digit); <strong>Enter</strong> on Armed toggles ON/OFF. The configured time is shown next to the <strong>Alarm</strong> menu row when armed, and the setting persists across reboots.</p>
|
||||
<p>While an alarm is armed a bell icon signals it in two places: the top-left corner of the <strong>Clock page</strong> itself, and the <strong>top status bar</strong> of the other home pages (the status bar is hidden on the Clock page, which is why the clock face carries its own indicator). The bell is icon-only — the exact alarm time is on the <strong>Alarm</strong> row inside Clock Tools.</p>
|
||||
|
||||
@@ -1276,6 +1276,17 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#keyboard" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Keyboard
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1512,6 +1523,17 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#keyboard" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Keyboard
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1815,6 +1837,25 @@
|
||||
</tbody>
|
||||
</table>
|
||||
<hr />
|
||||
<h3 id="keyboard">Keyboard</h3>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Setting</th>
|
||||
<th>Options</th>
|
||||
<th>Notes</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Layout</td>
|
||||
<td>ABC / T9</td>
|
||||
<td>On-screen keyboard style. <strong>ABC</strong>: an a-b-c…z grid, one key per letter (the original layout). <strong>T9</strong>: phone-keypad multi-tap — each key is labelled with its <strong>digit</strong> and a letter group (e.g. <code>2abc</code>); repeated <strong>Enter</strong> presses cycle through the letters and then the digit itself.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>Applies to every on-screen text field (messages, waypoint labels, room passwords, preset names). Earlier releases labelled the grid <em>QWERTY</em>; the layout has always been alphabetical, so it is now named <strong>ABC</strong>.</p>
|
||||
<hr />
|
||||
<h3 id="contacts">Contacts</h3>
|
||||
<table>
|
||||
<thead>
|
||||
|
||||
@@ -1795,7 +1795,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>The Tools screen is a hub for GPS trail recording, nearby node browsing, ringtone editing, auto-reply bot, auto-advert, live location sharing, locator, compass, device diagnostics, and repeater mode. Tools are grouped into collapsible <strong>Location</strong> / <strong>Comms</strong> / <strong>System</strong> sections — the same fold-in-place model as Settings; Tools always opens folded back to the section list. Navigate with <strong>UP/DOWN</strong>, press <strong>Enter</strong> on a section header to expand or collapse it, or on a tool to open it.</p>
|
||||
<p>The Tools screen is a hub for GPS trail recording, nearby node browsing, ringtone editing, auto-reply bot, auto-advert, live location sharing, locator, compass, clock tools (alarm / timer / stopwatch), device diagnostics, and repeater mode. Tools are grouped into collapsible <strong>Location</strong> / <strong>Comms</strong> / <strong>System</strong> sections — the same fold-in-place model as Settings; Tools always opens folded back to the section list. Navigate with <strong>UP/DOWN</strong>, press <strong>Enter</strong> on a section header to expand or collapse it, or on a tool to open it.</p>
|
||||
<hr />
|
||||
<h2 id="nearby-nodes">Nearby Nodes</h2>
|
||||
<table>
|
||||
@@ -2082,6 +2082,11 @@ The <strong>Map</strong> view is also reachable directly from the home carousel
|
||||
<td>Off / 5 / 10 / 30 s — GPS averaging for <strong>Mark here</strong> (see Waypoints below)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Auto-save</td>
|
||||
<td>always</td>
|
||||
<td>Off / On — auto-write the live trail to flash on shutdown, so a <strong>low-battery auto-shutdown</strong> doesn't lose the route (see below)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Readout</td>
|
||||
<td>Summary view</td>
|
||||
<td>Summary shows Speed or Pace (in the global unit system)</td>
|
||||
@@ -2095,6 +2100,7 @@ The <strong>Map</strong> view is also reachable directly from the home carousel
|
||||
</table>
|
||||
<p>(Trail file… appears only when a live or saved trail exists. Mark here needs a GPS fix; Waypoints is always available.)</p>
|
||||
<p><strong>Auto-pause</strong> — when set, a recording trail automatically <strong>pauses</strong> after the device has stayed within ~15 m of one spot for the chosen delay: the elapsed timer and point sampling both freeze, and the map line breaks across the idle gap. It <strong>resumes on its own</strong> as soon as you move again. This keeps a stop (a break, a meal, parking) out of your distance and average-speed stats without you having to remember to stop and restart tracking. A paused trail is still "on" (the <strong>G</strong> marker keeps blinking) — the Summary <strong>Status</strong> row shows <code>paused</code>. The stop is detected with its own coarse movement gate, independent of <strong>Min dist</strong>, so GPS jitter while you're parked doesn't keep it awake.</p>
|
||||
<p><strong>Auto-save</strong> — with this on (default off), the live trail is written to flash automatically when the device powers off, so a <strong>low-battery auto-shutdown</strong> no longer discards the whole route. It saves to the same <code>/trail</code> file as the manual <strong>Trail file… → Save</strong>, and only writes when the trail actually has points — an empty trail can't overwrite a previously saved one. Off by default so a normal shutdown doesn't silently overwrite a saved trail you meant to keep.</p>
|
||||
<h3 id="track-back">Track back</h3>
|
||||
<p><strong>Hold Enter → Track back</strong> retraces the trail you just recorded, back to where you started — useful for returning the same way in poor visibility or unfamiliar ground. It reuses the navigation view (distance + two absolute bearings; see <em>Waypoints › Navigating</em>), but instead of a single fixed target it walks the recorded breadcrumbs in reverse: it snaps onto the route at the <strong>nearest recorded point</strong>, guides you to it, then automatically advances to the next earlier point as you reach each one (within ~20 m). The header shows how many points remain (<code>Back: 12 pt</code>), reading <code>Trail start</code> on the final leg; arriving there shows <code>Back at start</code> and exits. <strong>Cancel</strong> leaves track-back at any time. It needs a trail with at least two points and a GPS fix; it doesn't require tracking to still be running.</p>
|
||||
<h3 id="waypoints">Waypoints</h3>
|
||||
|
||||
Reference in New Issue
Block a user