For type-safety and light callback, someone may be interesting about this.
Once a time, I worked out a prototype when I need the signal-slot
mechanism in my embedded environment.Please take a look at
https://code.google.com/p/c-sigslot/downloads/list.
The implementation is based on standard longj
On Mon, 14 Feb 2011 20:32:48 +0100
Benjamin Otte wrote:
> For now, I'm interested in high-level review of the idea. Things like
> "This whole idea is stupid because ...", "I would change the API so
> that ...", "If you did this, we could also use it for ...", "How do
> you intend to solve ..." or
Because there is not enough people taking care of that backend and it
was broken most of the time.
2011/3/19 zhangzhao130181 :
> Why gtk3.0 or newer does't support DirectFB?
>
>
>
> ___
> gtk-devel-list mailing list
> gtk-devel-list@gnome.org
> http://m
Why gtk3.0 or newer does't support DirectFB?
___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list
libegg has lots of directories that have just a README saying how the
code has successfully moved into GTK+. But that's mostly old news now.
If there's no objection then I'll remove the directories so it's easier
to see at a glance what's still interesting.
--
murr...@murrayc.com
www.murrayc.com
Hey,
Is there any reason we don't have something similar to
G_DEFINE_CALLBACK() as described below in [1]? It seems like it would
increase type-safety a lot...
Thanks,
David
[1] : See [2] for compiler output
#include
/**
* G_DEFINE_CALLBACK:
* @function: The function to check
* @function_t
On Fri, 2011-03-18 at 14:13 +0800, czk wrote:
> hello everyone,
> I use gtk+-3.0 in a embedded device. If I create a window put 4
> buttons , 4 entrys 3 labels in it, from gtk_window_new to the window
> was showed spend 4 seconds totally. It a long time for me. Most time
> spend in gtk_widget_show
