Skip to content

README: mvvm.Queue needs go-widgets/mvvm v0.14.0 or later #144

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tannevaled merged 1 commit into from
Oct 11, 2026
Merged

README: mvvm.Queue needs go-widgets/mvvm v0.14.0 or later #144

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
<!-- docsym:allow mvvm.Queue mvvm.NewQueue -- application code: Queue is in mvvm v0.14.0+, and this module does not import mvvm itself -->
drain it in the root container's `SetBounds`, which every backend calls before it
draws:

Expand Down
Loading