Fwd: FileChooserDialog constructors taking backend argument

[Daniel Boles <dboles src gmail com>]

On 27 March 2017 at 12:50, Kjell Ahlstedt <kjell ahlstedt bredband net> wrote:

Den 2017-03-26 kl. 23:15, skrev Daniel Boles:

Hello,

About this commit: https://git.gnome.org/browse/gtkmm/commit/?id=bd97e557771cdce23bdc815288db2ffdd8c083c9

Clearly these constructors could not actually achieve their stated purpose in GTK+ 3, as the backend functionality was removed already then.

In case anyone was trying to use these in gtkmm-3, should deprecation warnings be added there, too? Clearly we don't want to just remove these ctors and break code that was using them, however ineffectively.

I have marked the FileChooserDialog constructors with backend parameters deprecated in gtkmm-3. I suppose it's almost okay to do that in the gtkmm-3-22 branch. We have been forced to deprecate other methods there because of recent deprecations in gtk+. According to normal rules, new deprecations would have to wait until gtkmm 3.24.
https://git.gnome.org/browse/gtkmm/commit/?h=gtkmm-3-22&id=db8310fc15108624c0d50bcbaf73312d59b297dc

Thanks!

Indeed, even GTK+ 3.22 is not strictly enforcing API freeze; as well as deprecations, there has recently been some new API added. One in particular that comes to mind is gtk_flowbox_get_child_at_pos():
https://git.gnome.org/browse/gtk+/commit/gtk/gtkflowbox.h?h=gtk-3-22&id=9679ef6b00cb087fecf772bb69ab9a2ad7429835

Shall we wrap such new methods when they arise?