| commit | fa2d039b2cda314e83cc9fd8fd5b9d41c09a0993 | |
| author | Gerd Hoffmann <kraxel@redhat.com> | |
| Wed, 14 Mar 2018 08:04:39 +0000 (14 09:04 +0100) | ||
| committer | Gerd Hoffmann <kraxel@redhat.com> | |
| Tue, 10 Apr 2018 09:22:02 +0000 (10 11:22 +0200) | ||
| tree | 40fb4dc5c9dcbf73dcc260ddcefc905989e00abe | treesnapshot (tar.gz zip) |
| parent | 1e70de679d2e7e1312d9c9debed8d11612d469d9 | commitdiff |
gtk: drop pointless code from gd_window_close
Unregistering the display change listener looks like a pointless
excercise given we'll exit in a moment. When exiting qemu via
menu/file/quit this will not happen either. Just drop the code.
Also return TRUE unconditionally. This will tell gtk to ignore the
close request, so gtk will not start destroying widgets and causing
warnings due to UI code trying to talk to widgets which are gone.
Just depend on qmp_quit() doing it's job instead.
Reported-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Message-Id: <20180314080439.4229-1-kraxel@redhat.com>
Unregistering the display change listener looks like a pointless
excercise given we'll exit in a moment. When exiting qemu via
menu/file/quit this will not happen either. Just drop the code.
Also return TRUE unconditionally. This will tell gtk to ignore the
close request, so gtk will not start destroying widgets and causing
warnings due to UI code trying to talk to widgets which are gone.
Just depend on qmp_quit() doing it's job instead.
Reported-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Message-Id: <20180314080439.4229-1-kraxel@redhat.com>
| ui/gtk.c | diffblobblamehistory |