On Wed, 2005-07-20 at 15:35 -0400, Chris Shoemaker wrote: > On Wed, Jul 20, 2005 at 08:19:40PM +0100, Neil Williams wrote: > > On Wednesday 20 July 2005 7:53 pm, Chris Shoemaker wrote: > > > > Why such a tortuous path? Split -> Collection -> Book. Checking the book > > automatically checks all collections. The Book won't know WHICH split has > > been changed so you gain nothing. > > Ah, I didn't realize the Collection's dirtiness propagated to the Book.
Terminology check here. As far as I can tell, in the current code dirtiness doesn't *propagate* anywhere. Checking whether the book is dirty automatically checks whether any of the collections are dirty. This is a "pull" system, not a "push" system. If gnucash was a push system I'd have everything I need to fix the dialog and the window title. David _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
