From f31063c87e800351ac6416ecdb0b3f9a1b842f7f Mon Sep 17 00:00:00 2001 From: Colomban Wendling Date: Sun, 26 Feb 2017 20:18:26 +0100 Subject: Bug [#1907]. GTK: Fix crash after destroying the widget on GTK < 3.3.6 On GTK2 and GTK3 < 3.3.6 there is no GtkAccessibleClass::widget_unset() method, so we can't destroy our accessible object right away. So, to avoid accessing a destroyed widget, we need to check whether the widget still exists in the the ScintillaGTKAccessible destructor. In other methods it's not necessary because the wrapping GObject class makes sure not to forward other when the widget has been destroyed, but we still have to destroy the C++ instance no matter what, so the check has to be on this side. --- doc/ScintillaHistory.html | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'doc/ScintillaHistory.html') diff --git a/doc/ScintillaHistory.html b/doc/ScintillaHistory.html index 35bad2ece..ad0910e52 100644 --- a/doc/ScintillaHistory.html +++ b/doc/ScintillaHistory.html @@ -535,6 +535,10 @@ Bug #1915.
  • + Fix crash in accessibility code on GTK+ < 3.3.6 caused by previous bug fix. + Bug #1907. +
    • +
  • Fix to prevent double scrolling on GTK+ with X11. Bug #1901.
    • -- cgit v1.2.3