On 5/30/07, Brian J. Tarricone [EMAIL PROTECTED] wrote:
Using an idle
function will chew through CPU cycles while the application is
otherwise idle (really hurts laptop battery performance, for one
thing). Another option is a timeout using g_timeout_add(), but the
correct approach would be
Good day, new to the list and GTK+ in general.
I am formerly a Macintosh developer. Currently however I am now working
on Objective C bindings for GTK+. I am currently looking at the
documentation for the run loop which I have found located at
http://developer.gnome.org/doc/GGAD/sec-mainloop.html
tir, 29 05 2007 kl. 18:12 -0500, skrev Dan Saul:
I am formerly a Macintosh developer. Currently however I am now working
on Objective C bindings for GTK+. I am currently looking at the
documentation for the run loop which I have found located at
On Tue, 29 May 2007 18:12:57 -0500 Dan Saul wrote:
Good day, new to the list and GTK+ in general.
I am formerly a Macintosh developer. Currently however I am now working
on Objective C bindings for GTK+. I am currently looking at the
documentation for the run loop which I have found located at
Replying to myself...
On Tue, 29 May 2007 16:29:12 -0700 Brian J. Tarricone wrote:
Actually, you might want to poke around in gdk/quartz/ inside gtk+
SVN. I imagine autorelease pools are used in the MacOSX backend; maybe
you can find some hints there as to what's best.
I was curious, so I
On Tue, 2007-29-05 at 16:29 -0700, Brian J. Tarricone wrote:
On Tue, 29 May 2007 18:12:57 -0500 Dan Saul wrote:
Good day, new to the list and GTK+ in general.
I am formerly a Macintosh developer. Currently however I am now working
on Objective C bindings for GTK+. I am currently looking
