On Thu, 2013-04-25 at 20:54 -0600, Michael Torrie wrote:
As both Chris and Colomban have state, triggering an event flush isn't
going to help. If the events are already getting filed up, trying to
flush them isn't going to work. You have to figure out why the events
are piling up. Because
On Thu, 2013-04-25 at 22:18 -0700, Simon Feltman wrote:
A brief look at the source and it seems there is nothing calling
Gdk.threads_init which I think is needed.
Hey Simon. I'm actually calling GObject.threads_init() over in Main.py.
I've been told by others that this is enough, whereas
Hi,
I already posted a while ago the same trouble, but still no definitive
answer. I work with Gtk3, I did not tried that on Gtk2.
There is actually a behavior bug on systray menu in Gnome3 and KDE4.
Only those, all other WMs/DMs are working properly.
I opened a bug for each, no answers
Il Fri, 26 Apr 2013 02:24:01 -0700 Kip Warner k...@thevertigo.com scrisse:
On Thu, 2013-04-25 at 22:18 -0700, Simon Feltman wrote:
Similarly, use
Gdk.threads_add_idle instead of GObject.idle_add for scheduling GUI updates
from worker threads. The necessity of these is still somewhat
Le 26/04/2013 03:59, Kip Warner a écrit :
On Sat, 2013-04-20 at 18:54 +0200, Colomban Wendling wrote:
Just never do something time consuming in the main loop thread. If you
don't there should not be any lag.
Hey Colomban. The time consuming task is in its own separate thread, but
it's
On Fri, 2013-04-26 at 15:16 +0200, Colomban Wendling wrote:
That's weird. However, although I don't know much about Python
threading (and another guy in this thread suggests it's not really
good), I'm wondering whether your thread couldn't be simply locking
stuff used by both GUI and worker
On Fri, 2013-04-26 at 13:52 +0200, Nicola Fontana wrote:
gdk_threads_add_idle() is only a convenient way of calling
g_idle_add()
without the need of decorating the callback code with a
gdk_threads_enter()/gdk_threads_leave() pair:
Hello,
I have a GtkDrawingArea inside a GtkViewport, and I have a callback
connected to the size-allocate signal of the GtkViewport which resizes
the GtkDrawingArea by calling gtk_widget_set_size_request on the latter,
see sample source code below.
I however notice that the GtkDrawingArea
On Fri, Apr 26, 2013 at 6:16 AM, Colomban Wendling
lists@herbesfolles.org wrote:
That's weird. However, although I don't know much about Python
threading (and another guy in this thread suggests it's not really
good), I'm wondering whether your thread couldn't be simply locking
stuff
