2018-11-07 Kjell Ahlstedt 3.22.1 2018-11-07 Kjell Ahlstedt Link to glibmm 2.58 It's the latest glibmm version in the glibmm-2.4 ABI series. This ABI series is compatible with gtkmm3. 2018-10-27 Daniel Boles Clarify that user sometimes must delete if managed container.ccg remembers whether the object was originally un-floated by Gtk::manage() and, if so, restores that state during Container.remove(), with the result that the removed widget is *not* deleted, as it would be in GTK+, but instead it is re-floated and requires the user to deal with (e.g. to add it to some other container or to finally call delete on it) This is documented in container.hg but nowhere that I can see in our tutorial, and I think it is worth mentioning here, since it is not completely intuitive: users might otherwise think that the fact manage() delegates lifetime management to the Container means they get back the same behaviour of C widgets, i.e. that remove() would cause destruction, but of course that is not the case, and we might thus encourage leaks. So mention that manage() only relieves the user of the burden of calling delete if they add the widget to a parent and do not remove it later, in both the Memory Management section and the part about deleting wrappers. 2018-10-26 Kjell Ahlstedt configure.ac: Update bug report address 2018-05-31 Kjell Ahlstedt Fix a broken link to www.gtkmm.org Fixes #2 2018-01-15 Daniel Boles Fix typo in my recent ColumnRecord commit Thanks to Kjell for pointing this out. https://bugzilla.gnome.org/show_bug.cgi?id=792482#c10 2018-01-14 Daniel Boles Fix 2 typos of slot_callbback => slot_callback 2018-01-14 Daniel Boles Don’t write main() without a return type Yikes! That’s not C++. 2018-01-14 Daniel Boles Clarify: ColumnRecords can be static *singletons* Sharing these between models is highly desirable as it can avoid a lot of work and waste. So, take the para warning about not making static ColumnRecords, and reword it to explain why you probably wanted a static one and what the real solution is. https://bugzilla.gnome.org/show_bug.cgi?id=792482 2017-12-28 Kjell Ahlstedt Don't use the deprecated Gdk::screen_width() and screen_height() 2017-11-15 Kjell Ahlstedt Clarify when the user shall delete the wrap() result There are situations when the user is responsible for deleting the wrap() result. Bug 788646 2017-11-15 Daniel Boles Mixing C & C++: Clarify ownership of wrap() result Make it clear that wrap() returns a pointer to an instance owned by glibmm, so users should not try to delete it. Also mention the effect on refcount, i.e. nothing if (!take_copy). Finally, show the C++ instance actually being used (though a better example would show more advantage). While here, I split the long paragraphs for readability & to help git, & add some missing / tags for readability/semantics. https://bugzilla.gnome.org/show_bug.cgi?id=788646 2017-11-01 Kjell Ahlstedt Fix buildapp/Makefile.am and buildapp/README * examples/book/buildapp/Makefile.am: Fix the build of resources.c in steps 8 and 9. * examples/book/buildapp/README: Describe how to make the application find the saved preferences. 2017-02-01 Kjell Ahlstedt Headers and Linking section: Replace broken link Replace the link to Openismus with links to GNU's documentation of autoconf and automake. Bug 777879