GTKʼs GtkSearchEntry is NOT a GtkEntry, but gtkmmʼs Gtk::SearchEntry IS a Gtk::Entry
The title says it all really. In GTK the SearchEntry
is no longer derived from Entry
, but in gtkmm it is... meaning we can ostensibly use Gtk::Entry
API on a Gtk::SearchEntry
, and it builds, but it fails at runtime because the GTK/GObject cast to a GtkEntry
of course does not succeed. This is far from ideal!
I don't know what to do here. Having an irrelevant C++ wrapper class in the hierarchy is obviously bad, but I guess we can't remove that until gtkmm 5 now. Can we maybe add a new 'copy' (named... who knows what) - which has the correct inheritance hierarchy - and loudly deprecate the existing Gtk::SearchEntry
in favour of that?