spoopyghosty0--frameport

0 Fork 0

mirror of https://github.com/spoopyghosty0/frameport.git synced 2026-10-17 18:03:05 +02:00

Files

T

spoopyghosty0 f7108c0ca4 Fix: a page change could die when a background thread set a control property mid-update

Flet packs a patch by iterating each control's _values dict; Prop.__set__ adds/removes keys there without a lock.
A property set on a background thread (the live Frame card's sample, job progress, the library loader) while the
event loop packed a patch raised "dictionary changed size during iteration" and the update was lost (seen in CI:
a sidebar click left the old page showing). serialize_flet_updates() now makes property writes take the same
re-entrant lock as patches (app.FLET_LOCK). Reproduced with Flet's own encoder: 16 failures in 4 s before, none
after; test_property_writes_wait_for_a_patch_being_packed. The showcase server and ui_smoke serialize like the app.
Tour re-recorded with the fix (clean, no fallback clicks).

2026-10-09 08:04:55 -04:00

showcase

Fix: a page change could die when a background thread set a control property mid-update

2026-10-09 08:04:55 -04:00

catalog_from_issue.py

Catalog: working configs from issues #1 (Resident Evil 4, package com.Armature.VR4: works with issues), #3 (Cook-Out), #6 (Beat Saber), #11 (Job Simulator), #12 (Dinosaur Island); games list regenerated. catalog_from_issue: 'device' is a checked list field, and FramePort patch ids must exist

2026-10-04 00:52:39 -04:00

compat_list.py

UI text: snooze for Later, Frame picker, clear labels, tr() everywhere, one vocabulary

2026-10-07 21:50:21 -04:00

dev_version.py

Dev builds on demand: CI "Run workflow" (dev ticked, optional notes for testers) publishes the rolling dev pre-release with version <next patch>.dev<run>; Settings → Updates → "Install the latest dev build…" installs it like an update (automatic checks still ignore it; the next release is offered normally)