Re: gtkmm 3.4.0 (gtk 3.4.2) multithread app graphic deterioration
- From: Kjell Ahlstedt <kjell ahlstedt bredband net>
- To: Chris Vine <chris cvine freeserve co uk>
- Cc: Gtkmm list <gtkmm-list gnome org>
- Subject: Re: gtkmm 3.4.0 (gtk 3.4.2) multithread app graphic deterioration
- Date: Mon, 09 Jul 2012 16:59:31 +0200
2012-07-09 12:05, Chris Vine skrev:
Glib::SignalIdle.connect_once() is hoped to be thread safe as of about
2 months' ago provided that the slot object does not represent a
non-static method of a class deriving from sigc::trackable, but I don't
think that has hit a main release yet. ("Hoped to be" means that I
don't think anyone has stress tested it yet, but the code was committed
some 2 months' ago.)
Hi Chris,
I suppose you refer to the changes mentioned in bug
https://bugzilla.gnome.org/show_bug.cgi?id=396963, which you helped me
to get (hopefully) correct. Those two commits were pushed on April 3 and
4, and they are included in glibmm 2.32.
Kjell
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]