diff options
| author | Emmanuele Bassi <ebassi@gnome.org> | 2018-02-02 16:34:40 +0100 |
|---|---|---|
| committer | Emmanuele Bassi <ebassi@gnome.org> | 2018-02-03 12:07:10 +0100 |
| commit | 888dfe499d92a434c3ce703df7057c4703a6c75e (patch) | |
| tree | 91e393aadfe75f32a819f9e78deac024977918dd /NEWS.pre-1.0 | |
| parent | c655759cefa56efdb0cb943bb5dada3ff75a963c (diff) | |
| download | gtk+-888dfe499d92a434c3ce703df7057c4703a6c75e.tar.gz | |
Drop the Big GDK Lock
GDK has a lock to mark critical sections inside the backends.
Additionally, code that would re-enter into the GTK main loop was
supposed to hold the lock.
Back in the Good Old Days™ this was guaranteed to kind of work only on
the X11 backend, and would cause a neat explosion on any other GDK
backend.
During GTK+ 3.x we deprecated the API to enter and leave the critical
sections, and now we can remove all the internal uses of the lock, since
external API that uses GTK+ 4.x won't be able to hold the GDK lock.
https://bugzilla.gnome.org/show_bug.cgi?id=793124
Diffstat (limited to 'NEWS.pre-1.0')
0 files changed, 0 insertions, 0 deletions