FileChooserButton signals (was 2.16 API freeze / checking new API)
- From: Murray Cumming <murrayc murrayc com>
- To: Damon Register <damon w register lmco com>
- Cc: gtkmm-list <gtkmm-list gnome org>
- Subject: FileChooserButton signals (was 2.16 API freeze / checking new API)
- Date: Tue, 10 Feb 2009 11:36:29 +0100
On Tue, 2009-02-10 at 05:21 -0500, Damon Register wrote:
> In that thread from last year I had asked about getting a notification
> from a FileChooserButton when I have returned from the dialog with a
> valid file selection (double clicking on the file or clicking open).
> If I remember correctly, Gtk::FileChooser::signal_file_activated()
> didn't work then (May 16, 2008). Perhaps I am using incorrectly but
> it seems that Gtk::FileChooser::signal_file_activated() still doesn't
> work.
I investigated.
The file-set signal was added in GTK+ 2.14:
http://library.gnome.org/devel/gtk/unstable/GtkFileChooserButton.html#GtkFileChooserButton-file-set
It was not wrapped in gtkmm 2.14 because it is a G_ACTION_SIGNAL, which
are usually not public API. But looking at the bug that added it, I
think that it is meant to be used by applications:
http://bugzilla.gnome.org/show_bug.cgi?id=353196
I have added it in svn trunk so it will be in gtkmm 2.16. In the
meantime you may it via the C API with gobj().
--
murrayc murrayc com
www.murrayc.com
www.openismus.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]