I had a bug filed on this lack of warning: https://bugs.gnucash.org/show_bug.cgi?id=796978, which it looks like Bob had a fix pushed for 3.4.
I don’t think I’ve tested it since. I’ll give it a go and see what happens. Ideally, the check for lack of an anchoring split shouldn’t happen till the user commits the transaction. If editing is still going on, the user might still add an anchoring split. But that would be another bug report or an RFE. Regards, Adrien > On Jun 5, 2019, at 1:56 PM, David T. via gnucash-user > <gnucash-user@gnucash.org> wrote: > > > David, > > If you delete the split for the current register, there is nothing binding > the transaction to the current register, so of course it will "disappear" > from this register. > > David > > > On Wed, Jun 5, 2019 at 14:49, David Carlson<david.carlson....@gmail.com> > wrote:... > > The main caveat is if that is done in the last or only row containing the > account register name of the current view, the entire transaction seems to > disappear out of that register view without warning, but it still exists in > the general ledger and the register views of the other split lines. In my > case that process takes several seconds and it is irreversible if done by > accident. > _______________________________________________ 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.
