Thanks David,
David Carlson-4 wrote > I believe one important take-away from this thread is that there are many > ways to use scheduled transaction s and there is no one best way that > works > for all users. > > If a developer were to tackle some of the bugs and feature requests in > this > area it would be important to avoid "breaking" one use to optimize > another. > > David Carlson > _______________________________________________ I agree with you on the importance of avoiding the breakage of one useful feature to optimise another, but evolutionary improvements are only made when a need is flagged up and deemed worthy of implementation. Sometimes, (often) dismantling followed by reassembly can achieve significant improvements, which is the way I assume GnuCash has evolved. Thanks to all developers for the efforts involved. Alan -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
