Re: filechooserdialog

On 03.08.2012 23:57, Dave M wrote:
Now for the general GtkResponseType problem.  Unfortunately, I don't see an
easy way to solve the problem nicely in one go.  The issue is that all
arguments and return values that conceptually are of type GtkResponseType,
are actually marked as a plain gint so that C users can pass in values that
are not actually in the pre-defined enum.  So we would have to go through
each occurrence of GtkResponseType and add an override that does the
%reponse_code dance like above.  I think these are all cases:

â gtk_dialog_new_with_buttons, gtk_dialog_run, gtk_dialog_response,
gtk_dialog_add_button, gtk_dialog_add_buttons, gtk_dialog_add_action_widget,
gtk_dialog_set_default_response, gtk_dialog_set_response_sensitive,
gtk_dialog_get_response_for_widget, gtk_dialog_get_widget_for_response,
gtk_dialog_set_alternative_button_order_from_array (these last two probably
also need some annotation work first)
â GtkDialog's "response" signal

I've now finally managed to get this sorted with the recent round of commits to Glib::Object::Introspection and Gtk3.

â gtk_file_chooser_dialog_new

And I committed your patch for this.

This only leaves:

â gtk_recent_chooser_dialog_new, gtk_recent_chooser_dialog_new_for_manager
â gtk_info_bar_new_with_buttons, gtk_info_bar_add_action_widget,
gtk_info_bar_add_button, gtk_info_bar_add_buttons,
gtk_info_bar_set_response_sensitive, gtk_info_bar_set_default_response,
â GtkInfoBar's "response" signal

Are you up for tackling these?

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