1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
//! Thread-local draw-request and invalidation signals.
//!
//! Two independent channels feed the host's event loop:
//!
//! 1. **Immediate draw request** — [`request_draw`] / [`wants_draw`]. Any
//! widget whose visual output just changed calls `request_draw()`; the next
//! iteration of the host loop draws a frame and clears the flag. The same
//! call advances [`invalidation_epoch`], letting event dispatch dirty the
//! affected retained ancestor path even when the event bubbles as ignored.
//!
//! 2. **Scheduled draw** — [`request_draw_after`] /
//! [`peek_next_draw_deadline`]. A
//! widget that needs a draw *at a future time* (text-cursor blink,
//! tooltip delay) calls `request_draw_after(Duration)`; the host's
//! loop goes to sleep with `ControlFlow::WaitUntil(that_instant)` and
//! draws when the deadline fires. Successive calls keep the EARLIEST
//! deadline.
//!
//! The scheduled channel is read **non-destructively** via
//! [`peek_next_draw_deadline`]: a host re-arms its `WaitUntil` from the same
//! pending deadline on every idle iteration, so an intervening event that
//! does not itself repaint can no longer strand the wake (the reactive-host
//! "lost wakeup" that stalled tooltips, cursor blink, and scrollbar fades).
//! Once a pending deadline comes due, [`wants_draw`] observes it, clears the
//! cell, and raises the immediate-draw flag — a due deadline is deliberately
//! made indistinguishable from a plain [`request_draw`], upholding the
//! framework invariant that *anything needing a future draw eventually makes
//! `wants_draw()` true by itself*. Consumers re-arm during the ensuing paint,
//! which keeps recurring timers alive.
//!
//! The host loop draws iff `wants_draw()` (now inclusive of due deadlines).
//! Between draws it idles with `WaitUntil(peek_next_draw_deadline())`; no
//! frames are drawn while nothing has changed.
use Cell;
use ;
use ;
use Duration;
use Instant;
// ── Draw-request provenance trace ─────────────────────────────────────────────
//
// A thread-local ring buffer of `&'static str` reason tags, appended by the
// `*_tagged` request helpers below. It exists to answer one question that a
// stack-free thread-local signal otherwise makes impossible: *who* keeps the
// reactive host awake when the app should be idle? When the quiescence
// regression guard (demo-ui) finds the app still wants a draw after settling,
// it drains this buffer and names the culprits in its failure message.
//
// Cost: recording is compiled out entirely in release (`debug_assertions`
// off) so shipping hosts pay nothing. In debug/test builds each tagged
// request pushes one pointer-sized tag into a small capped `Vec`.
thread_local!
/// Cap on retained trace tags — a soft ring buffer: oldest tags drop once the
/// cap is hit so a long-running session can't grow the buffer unbounded.
const DRAW_TRACE_CAP: usize = 512;
/// Drain and return the recorded draw-request provenance tags (debug builds
/// only; always empty in release). Tests call this after driving frames to
/// name whatever kept the reactive host awake.
/// [`request_draw`] with a provenance tag — see the trace module docs. Prefer
/// this from library call sites so the quiescence guard can attribute wakeups.
/// [`request_draw_after`] with a provenance tag — see the trace module docs.
thread_local!
/// Advance the pointer-press epoch. Called by [`App`](crate::App) once per
/// pointer press that is about to be routed into the widget tree.
/// Current pointer-press epoch — see [`bump_pointer_press_epoch`]. Two
/// presses are *consecutive* (nothing pressed in between) exactly when their
/// observed epochs differ by one.
/// Process-global counter bumped by [`signal_async_state_change`] from
/// any thread. The async fetch / decode runs on a background worker
/// (e.g. ehttp's `std::thread::spawn`), so thread-locals it sets are
/// invisible to the main event loop. The main thread pumps this
/// atomic into its own thread-local epochs on every
/// `wants_draw` / `invalidation_epoch` / `async_state_epoch` read —
/// see [`pump_async_wakeup`].
static ASYNC_WAKEUP_COUNTER: AtomicU64 = new;
// ── Host waker ───────────────────────────────────────────────────────────────
//
// Bumping `ASYNC_WAKEUP_COUNTER` is only half the story for a *reactive* host.
// The main thread merges the bump in `pump_async_wakeup`, but that runs only
// when something already made the host read `wants_draw()` / an epoch. A host
// parked in winit's `ControlFlow::Wait` (or `WaitUntil` with a far deadline) is
// not executing at all, so a worker-thread `signal_async_state_change` would
// sit unobserved until an unrelated OS event happened to wake the loop.
// Consumers otherwise have to paper over this with a per-frame keep-alive
// repaint, which burns a core to stay idle.
//
// The optional host waker closes that gap: the host installs a cheap,
// thread-safe nudge (typically `EventLoopProxy::send_event`) once at startup,
// and `signal_async_state_change` calls it right after the atomic bump so the
// woken loop is guaranteed to observe the new counter value.
type HostWaker = ;
/// Process-global waker slot. Locked only to clone the `Arc` out; the waker
/// itself always runs with the lock released (see [`signal_async_state_change`]).
static HOST_WAKER: = new;
/// Install (or replace) the process-global host waker.
///
/// Call this once from a reactive host's startup path, passing a closure that
/// nudges the event loop awake — on winit that is
/// `move || { let _ = proxy.send_event(UserEvent::Wake); }`. Whenever any
/// thread calls [`signal_async_state_change`], the waker fires *after* the
/// cross-thread counter has been bumped, so the host is guaranteed to see the
/// pending wakeup on its next `wants_draw()` read.
///
/// Requirements on `waker`:
/// * **Cheap** — it runs inline on whatever worker thread finished an async
/// load; do no real work in it, just signal.
/// * **Thread-safe and non-reentrant** — it may be called from any thread and
/// must not call back into `signal_async_state_change`.
/// * **Failure-tolerant** — a closed event loop should be ignored (drop the
/// `send_event` error) rather than panicking.
///
/// Hosts that already pump every tick — the wasm `requestAnimationFrame` loop,
/// game-style continuous redraw hosts, and the headless test harnesses — do not
/// need a waker; they reach `pump_async_wakeup` on their own schedule.
/// Remove any installed host waker, restoring the plain counter-only behaviour.
///
/// Hosts call this on shutdown so a dangling `EventLoopProxy` isn't retained;
/// tests call it to reset this process-global slot between cases.
/// Clone the installed waker out of its lock, if any. The clone exists so the
/// call site can release the lock before invoking arbitrary host code.
/// Merge any pending cross-thread async-wakeup bumps into the calling
/// thread's draw/invalidation/async-state state.
///
/// Without this, an ehttp callback completing on a background thread
/// bumps thread-locals the main event loop never reads — the markdown
/// SVG-badge "wrong scale until any other event" bug, where the loop
/// keeps polling (`needs_draw=true` while `ImageState::Loading`) but
/// `invalidation_epoch` never changes, so `render_app_frame` skips
/// the layout pass and paints the freshly-decoded SVG into the
/// previous layout's placeholder rect.
/// Request that the host schedule another draw as soon as possible.
///
/// **This is the right default for every widget state mutation that affects
/// visual output.** Calling it from inside an `on_event` handler advances
/// [`invalidation_epoch`]; `dispatch_event` reads that epoch before/after
/// delivery and automatically calls `mark_dirty` up the ancestor path when
/// it sees a bump — so a retained ancestor's backbuffer cache invalidates
/// without the widget needing to know about that ancestor at all.
///
/// Without the epoch bump, a `Widget::on_event` that returns `Ignored` (the
/// common case for `MouseMove`) leaves the ancestor cache thinking
/// "nothing changed", and the next frame composites a stale bitmap. Hover
/// effects, focus rings, and any other appearance change driven by event
/// state ALL need this hook.
///
/// Reach for [`request_draw_without_invalidation`] only when you're certain
/// no retained widget's *content* changed — overlays, position-only
/// translations, and similar. When in doubt, use `request_draw`.
/// Request a frame **without** advancing [`invalidation_epoch`].
///
/// `dispatch_event` won't mark retained ancestors dirty for this call, so
/// any widget that drew its previous frame into a backbuffer cache will
/// composite the cached bitmap unchanged. Use this **only** when:
///
/// * The change lives in an app-level overlay that paints fresh every
/// frame outside any retained subtree (inspector hover rectangle, popup
/// menus rendered via `paint_global_overlay`, scroll-fade decorations).
/// * The change is position-only — a window drag-move, where the cached
/// content is reused at a translated origin (see `Window::on_event` for
/// the canonical example).
///
/// **Do NOT call this from a widget that mutated its own state and expects
/// the next paint to reflect it.** That's [`request_draw`]'s job. Hover
/// indices, focus changes, animation ticks, button-press states — anything
/// where the *content* of a retained widget differs from the cached
/// bitmap — must call `request_draw` so the cache invalidates. The
/// `MenuBar` hover regression in `widgets/menu/widget/tests_2.rs` exists
/// precisely because this distinction was missed once already.
/// Non-destructive read of the immediate-draw signal, *plus* the promotion
/// point for a due scheduled deadline. Hosts call this after drawing to
/// decide control-flow for the next loop iteration.
///
/// Pumps any pending cross-thread async-wakeup bumps first, so a fetch
/// callback that finished on a worker thread between frames is reflected
/// in the result.
///
/// If no immediate draw is pending but a [`request_draw_after`] deadline has
/// come due (`Instant::now() >= deadline`), this clears the scheduled cell and
/// raises [`NEEDS_DRAW`], returning `true`. That makes a due deadline
/// indistinguishable from an immediate [`request_draw`]: the normal
/// request_draw → paint → [`clear_draw_request`] cycle then applies, and
/// consumers re-arm their next deadline during that paint (so recurring timers
/// stay alive). This is what lets a purely reactive host serve scheduled
/// draws without relying on a `WaitUntil` surviving intact — see the module
/// docs on the lost-wakeup fix.
/// Monotonic draw-request epoch used to detect visual changes during dispatch.
///
/// Pumps cross-thread wakeups first so a background-thread
/// [`signal_async_state_change`] is observed here on the next read,
/// causing layout-key caches keyed on this epoch to re-layout.
/// Note that an async-side state change happened (image loader finished,
/// font loaded, etc.). Safe to call from any thread; the main event
/// loop observes the bump via [`pump_async_wakeup`] on its next
/// `wants_draw` / `invalidation_epoch` / `async_state_epoch` read.
///
/// This used to only bump thread-local epochs, which silently broke
/// when callers ran on background threads (ehttp spawns its own
/// `std::thread`) — the main thread never observed the change and
/// `render_app_frame`'s layout-key cache skipped the layout pass that
/// would have given freshly-decoded SVG badges their natural
/// dimensions (the user-visible "wrong scale until any other event"
/// bug).
///
/// If a host waker is installed ([`set_host_waker`]), it is invoked after the
/// cross-thread bump so a reactive host parked in `ControlFlow::Wait` wakes and
/// observes the already-published counter value.
/// Current async-state epoch. Backbuffer caches store this and force
/// a re-raster when it doesn't match.
///
/// Pumps cross-thread wakeups first so a worker-thread
/// [`signal_async_state_change`] surfaces on the next read.
/// Reset the per-frame draw flags. The `App::paint` entry point calls
/// this before delegating to the root widget so each frame starts fresh —
/// widgets that still need a draw (animation in flight, focus blink, etc.)
/// must re-arm during their draw, otherwise the loop goes idle.
///
/// Pending cross-thread async wakeups are *merged* first (advancing
/// [`invalidation_epoch`] and [`async_state_epoch`]) and only then is the
/// immediate flag cleared. Merging — rather than just marking the counter
/// seen — means a worker-thread [`signal_async_state_change`] landing after
/// the host's last `wants_draw()` but before `App::paint` still reaches that
/// paint's async-state dirty walk instead of being silently swallowed.
/// Clearing the flag afterwards keeps the old guarantee that a stale bump
/// cannot reappear on the next `wants_draw` read (parallel tests calling
/// [`signal_async_state_change`] must not leak wakeups into unrelated tests
/// that rely on `wants_draw()` returning `false` after a clear).
/// Clear **only** the immediate draw request ([`request_draw`]'s flag).
///
/// For a host that tried to draw and could not — the surface refused the
/// frame (swap chain backing off after a failed configure, window occluded).
/// That frame never reaches `App::paint`, the only other place the flag is
/// cleared, so left set it keeps `wants_draw()` true and a reactive host
/// spinning in `ControlFlow::Poll`. The host has already arranged its own
/// wake for the retry.
///
/// Unlike [`clear_draw_request`], this leaves the scheduled deadline
/// ([`request_draw_after`]) in place — it may be the very wake that retries
/// the frame. It also does not pump pending cross-thread
/// [`signal_async_state_change`] bumps; they merge on the next read, where
/// they both advance [`async_state_epoch`] and raise a draw request (whereas
/// `clear_draw_request` merges them into the epochs and then clears the
/// resulting request, since the paint it precedes consumes them).
/// Schedule a future draw. Keeps the EARLIEST pending deadline, so multiple
/// widgets asking for different delays will all be served by the soonest one
/// (each widget re-arms its own deadline on the next draw anyway).
/// Side-effect-free snapshot of the two draw signals for diagnostics.
///
/// Returns `(immediate_flag, next_deadline)` read straight from the
/// thread-local cells. Unlike [`wants_draw`], this does **not** pump
/// cross-thread async wakeups and does **not** promote or clear a due
/// deadline — reading it can never perturb the very runaway a caller is
/// trying to capture. Used by [`crate::debug_draw_report`].
/// Non-destructive read of the earliest pending scheduled-draw deadline.
///
/// Hosts arm `ControlFlow::WaitUntil(t)` from this on every idle iteration.
/// Because it does **not** clear the cell, re-arming is idempotent: an
/// intervening event that does not itself repaint cannot strand the scheduled
/// wake (the reactive-host lost-wakeup bug). The cell is cleared only when
/// the deadline actually comes due — [`wants_draw`] promotes it to an
/// immediate draw — or by [`clear_draw_request`] at the start of a paint,
/// after which consumers re-arm.
// ── Tween ────────────────────────────────────────────────────────────────────
//
// Small reusable time-based interpolator for widgets that want a smooth
// transition between two scalar states (hover ↔ dormant, off ↔ on, etc.).
// Ease-out cubic; reversal preserves the current value so rapid toggles
// don't snap. Requests a draw automatically while in flight.
/// Smooth scalar tween between `0.0` and `1.0` (or any pair of values the
/// caller interprets). Drives animations such as the scroll-bar hover
/// expansion and toggle-switch on/off slide.