Re: gtkmm 3.4.0 (gtk 3.4.2) multithread app graphic deterioration
- From: Giuseppe Penone <giuspen gmail com>
- 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: Sun, 8 Jul 2012 20:10:26 +0200
I'm quite interested in what you say
In another posting you said your program does a lot of input-output.
You don't need threads just for that: you can set up a watch on a
file descriptor for the main GUI thread using
Glib::signal_io().connect(). GIO/giomm also has a wide range of
asynchronous IO functions where all the hard work is done for you.
even if I made something like this (I've always dedicated a thread to every different input), consider that anyway I need the gui thread not to be blocked when the input is
receiving large amounts of data.
I will do research following your tips, thank you.
Cheers,
Giuseppe.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]