Hello I am working on the implementation of GtkInfoBar [ http://developer.gnome.org/gtk/stable/GtkInfoBar.html]. It uses GtkMessageType [ http://developer.gnome.org/gtk/stable/GtkMessageDi...]. This types are currently define under Gtk::MessageDialog. It seems awkward to use Gtk::MessageDialog::INFO while working with Gtk::InfoBar class. Should I redefine the type under Gtk::InfoBar (i.e. Gtk::InfoBar::INFO) ? Should we have defined the type under Gtk::Message (non existing) module ? What is the more rubyish way ? In order not to break compatibility I would go with the redifinition: both Gtk::MessageDialog::ERROR Gtk::InfoBar::ERROR set to the same value (ERROR of GtkMessageType enum).
on 2012-01-20 20:32
on 2012-01-20 21:51
I am looking at Gtk::Dialog#add_buttons in order to implement Gtk::InfoBar#add_buttons. Can someone explain me the choices made for this implementation ? Why using gtk_dialog_add_button and not gtk_dialog_add_buttons ? Why freezing the object during the processus ? Why using 2 rbgtk_dialog_add_buttons_internal_* functions ? I would like to avoid a wrong implementation for Gtk::InfoBar#add_buttons and to understand a bit better the C code.
Please log in before posting. Registration is free and takes only a minute.
Existing account
(Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
Log in with Google account | Log in with Yahoo account
No account? Register here.