diff options
author | Emmanuele Bassi <ebassi@gnome.org> | 2021-06-09 18:11:10 +0100 |
---|---|---|
committer | Emmanuele Bassi <ebassi@gnome.org> | 2021-06-09 18:11:10 +0100 |
commit | 71be3a8de1c7a1d4d9712e30db343289e48d7b95 (patch) | |
tree | 17d0e9449bbb0207ed982125cf9811f6c40554af /docs | |
parent | 17373c3e778d8a39d68af3decef593b245fa808a (diff) | |
download | gtk+-71be3a8de1c7a1d4d9712e30db343289e48d7b95.tar.gz |
docs: Mention the ::damage-event signal in the migration guide
There is no replacement for damage event tracking.
Diffstat (limited to 'docs')
-rw-r--r-- | docs/reference/gtk/migrating-3to4.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/reference/gtk/migrating-3to4.md b/docs/reference/gtk/migrating-3to4.md index f286fc72dc..0ffe95a8b5 100644 --- a/docs/reference/gtk/migrating-3to4.md +++ b/docs/reference/gtk/migrating-3to4.md @@ -200,6 +200,9 @@ on a one-by-one basis: - If you were using `::map-event` and `::unmap-event` to track a window being mapped, you should use property notification for the [property@Gdk.Surface:mapped] property instead. + - The `::damage-event` signal has no replacement, as the only consumer + of damage events were the offscreen GDK surfaces, which have no + replacement in GTK 4.x. ### Set a proper application ID |