Re: Gtk::Builder and Gtk::FontChooserDialog



ApplicationWindow is a strange creature. I've filed a bug instead of adding _UNMANAGEABLE to it.
https://bugzilla.gnome.org/show_bug.cgi?id=767951

Commit that fixes AppChooserDialog and FontChooserDialog:
https://git.gnome.org/browse/gtkmm/commit/?id=654ca7fff766a46b7a426f301a8506e77ba35af3

Kjell

Den 2016-06-22 kl. 15:59, skrev Kjell Ahlstedt:
Gtk::Window and all classes that derive from Gtk::Window shall have an _UNMANAGEABLE directive in their .hg files. By mistake that directive is missing in ApplicationWindow, AppChooserDialog and FontChooserDialog. I'll fix it in the git repository. You can ignore the warning.

Kjell

Den 2016-06-21 kl. 19:00, skrev Phil Wolff:
When calling Gtk::Builder::get_widget () on a Gtk::FontChooserDialog specified in Glade as a top-level window, this warning is issued:

    gtkmm-WARNING **: gtkmm: Attempt to call Gtk::manage() on a Gtk::Window, but a Gtk::Window has no parent container to manage its lifetime.

While this is certainly true, the warning doesn't appear for similar instances of Gtk::AboutDialog or Gtk::ColorChooserDialog. Is there something special about the FontChooserDialog that warrants the warning?





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]