Yes, it simply not valid to construct an std::string, and hence nor a Glib::ustring, from a nullptr. So if any code in gtkmm is not converting a C nullptr string to a C++ "", that's a bug.
> Returns the currently active string in *combo_box*, or nullptr if none is selected. Saying nullptr in documentation like this is simply wrong, because it gets auto-translated from C but we don't change that to "" as we should (and I opened a bug for). That might be easier said than done though. Basically, any C nullptr should be mapped to a C++ empty string, and if it's not somewhere, there's probably a bug in the wrapping.
_______________________________________________ gtkmm-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gtkmm-list
