Den 2014-10-02 14:14, Ahmet Öztürk
skrev:
You can report a bug if you like, but I don't think it's necessary. I would have fixed it in the git repository right away, if it weren't for the fact that any added API now will require first creating a gtkmm-3-14 branch. That's easily done, but it's better to wait some time after the release of gtkmm 3.14.0, until we have more stuff that shall not go into a 3.14.x release.On Prş, 2014-10-02 at 09:54 +0200, Kjell Ahlstedt wrote:Den 2014-10-01 11:16, Ahmet Öztürk skrev:Hello everybody, According to the Gtk+ documentation GtkSearchEntry emits a "search-changed" signal besides the standard "changed" signal. https://developer.gnome.org/gtk3/stable/GtkSearchEntry.html#GtkSearchEntry-search-changed I could not find a counterpart for this signal in Gtk::SearchEntry. Is there a special reason why it is not wrapped? Is there a way to use the C signal in a Gtkmm program? Best regards, AhmetIt has probably just been overlooked. I'm sure it will be included in some future version of gtkmm. You can call the glib function g_signal_connect(), e.g. like so: void my_signal_handler(GtkSearchEntry* entry, gpointer user_data); g_signal_connect(my_search_entry_instance.gobj(), "search-changed", (GCallback)my_signal_handler, user_data); KjellThank you, Kjell. Shall I report a bug about it? |