geany/scintilla
Colomban Wendling cb8151b29b GTK: Avoid possible IdleWork() calls on destructed objects
The idle callback removal clause in the ScintillaGTK destructor got
broken in the last Scintilla update [1], leading to the callback not
being removed thus possibly running after the instance destruction.
Indeed, gdk_threads_add_idle() wraps g_idle_add() with a custom user
data, thus making the g_source_remove_by_user_data() call in the
destructor incorrect, as we give it our own user data, not GDK's
wrapper one.

Fix the callback removal not to use user data matching to avoid this.

Closes #1033.

[1] 4e5c321dda/

X-Scintilla-Bug-URL: https://sourceforge.net/p/scintilla/bugs/1827/
X-Scintilla-Commit-ID: d889200cd9de032e278745f48b9c3108ccfa5984
2016-05-12 15:02:15 +02:00
..
2016-04-29 01:12:20 +02:00
2016-04-29 01:12:20 +02:00
2016-04-29 01:12:20 +02:00
2015-09-20 18:39:15 +02:00
2016-04-29 01:12:20 +02:00

These files are from the Scintilla project, http://www.scintilla.org.

See License.txt for the Scintilla license.

We try to keep these files in sync with the official project; any
changes should be sent there first. Otherwise changes could cause
conflicts when we next update Scintilla.


Public header constants (include/*.h)
-------------------------------------
You should not add constants in header files - instead use
Scintilla.iface and HFacer.py.

Do not change the value of constants in header files as this will
break Scintilla's ABI.