f0a9ec0519
Because the framebuffer itself might be backed by a texture, which might have mipmapping enabled. If so then rendering to the framebuffer will make those mipmaps out of date. Technically we are flagging the framebuffer's mipmaps as dirty *before* they are, because the journal hasn't been flushed yet. But we need to do it early because ideally the next flush will both write the offscreen framebuffer contents and then read them for use in rendering to an onscreen framebuffer. And the `mipmaps_dirty` flag needs to be set before the read, so therefore we need to do it before the next journal flush. Fixes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3146 where the offscreen framebuffer in question is meta-background's `monitor->fbo`. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1664> |
||
|---|---|---|
| .. | ||
| cogl | ||
| cogl-pango | ||
| test-fixtures | ||
| tests | ||
| .gitignore | ||
| cogl-config.h.meson | ||
| cogl-mutter-config.h.in | ||
| config-custom.h | ||
| meson.build | ||