From 52e91b2efb983a5b2b9f739d3241a17edc3c6b29 Mon Sep 17 00:00:00 2001 From: tannevaled Date: Sun, 11 Oct 2026 19:24:36 +0200 Subject: [PATCH] README: mvvm.Queue needs go-widgets/mvvm v0.14.0 or later The README tells an application to post results to an mvvm.Queue. Queue arrived in mvvm v0.14.0, and this module builds against v0.9.0 (through toolkit), so an application copying the example needs mvvm at v0.14.0 or above in its own go.mod; the README now says so. Found by docsym (go-fleettools/fleettools), which looks names up at the version a module actually builds against; the docsym:allow comment records why this one is right. Co-Authored-By: Claude Opus 5.5 --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 3f493ba..13fe865 100644 --- a/README.md +++ b/README.md @@ -289,7 +289,11 @@ own COOP/COEP `cmd/serve`) lives in `test/`, in two tiers: Every backend that has a run loop to wake is a `Repainter`: X11, Wayland, GTK, macOS, Windows and the browser tab. `Repaint` is safe from any goroutine, but widget state is not, so post the change to an -[`mvvm.Queue`](https://github.com/go-widgets/mvvm) whose wake is `Repaint`, and +[`mvvm.Queue`](https://github.com/go-widgets/mvvm) whose wake is `Repaint` +(`Queue` is in go-widgets/mvvm **v0.14.0 or later**; this module itself builds +against an older mvvm, so an application that uses it requires +`github.com/go-widgets/mvvm` at v0.14.0 or above in its own go.mod), and + drain it in the root container's `SetBounds`, which every backend calls before it draws: