On Fri, 2007-02-02 at 18:01 -0700, Rob Barnes wrote:
> It seems to work fine without using g_idle and just using
> gdk_threads_enter()/gdk_threads_leave(). What do I gain from using g_idle?
Well you gain simplicity, and you can avoid the gdk locking stuff. Also
on some platforms, particularly win
You were exactly right. Adding gtk thread support and gdk_flush() fixed it.
On 2/2/07, Michael L Torrie <[EMAIL PROTECTED]> wrote:
>
> On Fri, 2007-02-02 at 16:02 -0700, Rob Barnes wrote:
> > I am using gtk_widget_queue_draw() already. The doc says,"Once the main
> loop
> > becomes idle (after th
On Fri, 2007-02-02 at 16:02 -0700, Rob Barnes wrote:
> I am using gtk_widget_queue_draw() already. The doc says,"Once the main loop
> becomes idle (after the current batch of events has been processed,
> roughly), the window will receive expose events for the union of all regions
> that have been i
I am using gtk_widget_queue_draw() already. The doc says,"Once the main loop
becomes idle (after the current batch of events has been processed,
roughly), the window will receive expose events for the union of all regions
that have been invalidated.", but this does not seem to be happening.
Placing
On Fri, 2007-02-02 at 12:20 -0700, Rob Barnes wrote:
> I'm trying to write a simple program that draws a moving polygon on the
> screen. I started with the scribble-simple example and modified to draw the
> moving shape by redrawing the shape in the background color in the previous
> position first
I'm trying to write a simple program that draws a moving polygon on the
screen. I started with the scribble-simple example and modified to draw the
moving shape by redrawing the shape in the background color in the previous
position first then drawing it in the foreground color in the current
posit
