[gtkada] Changes in GtkAda 2.24

[Emmanuel Briot]

> In the spec of Gtk.Radio_Button we have on lines 76-77:
>   --  the Null_List. You can later get the new group that is created with a
>   --  call to the Group subprogram below.
> This should be:
>   --  the Null_List. You can later get the new group that is created with a
>   --  call to the Get_Group subprogram below.

Fixed, thanks

> Line 83 in the spec of Gtk.Fixed is:
>   --  Deprecated since 2.20, Use Gtk.Widget.Set_Has_Window instead.
> But this procedure is missing in Gtk.Widget, so is Get_Has_Window.

Indeed, the comment you quoted is part of the automatically generated packages (so the doc comes from the C version of gtk3 doc), and the binding for gtk-widget.ads has not been updated to add these functions.
I have verified however than in the branch for GtkAda-gtk3, the functions do exist in the generated gtk-widget.ads



> In my code is this statement:
>   Return_Callback.Connect(Get_Popup_Window(Oct_Combo), 
>     "unmap_event", On_Combo_Unmap_Event'Access);
> But the Get_Popup_Window function has been removed from the Gtk.Combo package, why?
> I know the whole package is deprecated but in some of my cases Gtk.Combo_Box_Entry is not
> a good replacement. It doesn't have a "match_selected" signal like the entry completion
> has. I've filed a Gtk bug for this. It also wastes screen space because there is much
> more space between rows in the dropdown window than the old combobox has.

Get_Popup_Window is no longer part of gtk+ 2.x apparently. I think we might have been accessing the private field "popup" before, but since it is private we were not really meant to do that.
I do encourage you to migrate to the new gtk_combo_box, indeed, since gtk_combo has completely disappeared now in gtk+-3.
Perhaps Gtk.Combo_Box_Entry might be more appropriate for you.
gtk+-3 also has a Gtk.Combo_Box_Text

I can't say I know much about these widgets, so I can't really comment on the specific issues you are mentioning. Opening bugs with the gtk+ developers is indeed the way to go (though I suspect they will not look at bugs against gtk+ 2.x, only gtk+ 3.x)

Emmanuel