Jean-Luc Makiola
c30a153552
The agenda widget loaded and sliced its data in the provideGlance preamble and captured it as a non-reactive local. updateAll() reliably recomposes a live Glance session but does not reliably re-run that preamble, so a range change was redrawn against the stale slice (intermittently — only when no session was alive did it pick up the new range). This is the same platform limitation the month widget already works around. Mirror that pattern: load the widest selectable window once, store the range in per-instance Glance state (AGENDA_RANGE_KEY), read it reactively via currentState, and slice in the composition. The settings setter writes the state into each instance and recomposes, so a range change now reflects via plain recomposition regardless of session lifecycle. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
28 lines
703 B
Markdown
28 lines
703 B
Markdown
---
|
|
name: Crash report
|
|
about: Report a crash. Calendula can capture this for you (Settings → Report a problem, or the prompt after a crash) — it copies the report to your clipboard and prefills this form.
|
|
title: "Crash: "
|
|
labels:
|
|
- bug
|
|
- crash
|
|
- priority:high
|
|
---
|
|
|
|
<!--
|
|
Thanks for reporting a crash in Calendula!
|
|
|
|
If the app prefilled this for you, the crash report is already below — just add
|
|
what you were doing and submit. Otherwise, paste the report from your clipboard
|
|
into the code block. The report contains only app/Android/device versions and the
|
|
stack trace — no personal data or calendar content.
|
|
-->
|
|
|
|
### What happened
|
|
|
|
|
|
### Crash report
|
|
|
|
```
|
|
(paste the crash report here)
|
|
```
|