Register problem in 2.4.1 - release BLOCKED

[Phil Longstaff]

On Sun, 2011-02-06 at 22:22 +0100, Christian Stimming wrote:
> Am Sonntag, 6. Februar 2011 schrieb Christian Stimming:
> > > > If I enter a transaction with 2 splits, and the other account is open
> > > > already, the split doesn't show up.  However, if I alter the sort order
> > > > (maybe do anything which affects which splits are shown), it suddenly
> > > > appears.  In gnucash.trace, I see "CRIT <Gtk> gtk_widget_is_ancestor:
> > > > assertion `ancestor != NULL' failed" which might be related.
> > 
> > Update: r20207 (by alex.aycinena, "Modify Tax Info on Account Page to
> > display or not display sub-account info based on whether row is
> > expanded.") introduces some CRIT <gtk> warnings:
> > 
> >   CRIT <Gtk> gtk_tree_sortable_set_sort_func: assertion `sort_column_id >=
> > 0' failed
> 
> I've reverted parts of r20207 in r20251 because of those CRIT warnings (sorry 
> Alex). I hope Alex can sort out the cause of this issue and then re-revert my 
> r20251 later in a way that doesn't cause warnings anymore.
> 
> @Phil: Do you still see these gtk_widget_is_ancestor warnings?

No, they've gone away, and the other register behaviour problem is gone
as well.  I'll tag as 2.4.2.

Phil