bug: MEMO fields not synchronized in transfer

[Dave Peticolas]

Charlton Rose writes:
> GnuCash has a handy feature that allows it to "guess" the rest of an entry
> as soon as you complete the "DESCRIPTION" field.  The guess is derived
> from your previous input history and is often times right on the money
> (pun intended).
> 
> However, this feature also gives rise to a serious problem when the guess
> is not correct.  After completing the DESCRIPTION field, and seeing that
> the rest of the fields are automatically filled in with cached values, you
> may decide that one or more of the automatically filled-in fields require
> some tweaking.  If you tab over to the MEMO field and update it,
> everything *appears* to work fine.  But it is an illusion.  When you
> inspect the same entry in the other register, you will find that the MEMO
> field still contains the old (incorrectly) guessed value, and that your
> correction was completely ignored on the other end of the transfer.
> 
> This means that every time you have to correct the automatically filled-in
> MEMO field, you must also do it on the other side of the transfer as
> well.  This is a huge pain in the rear.

Thanks for the detailed bug report. What's going on is that the memo
field is associated with splits and not transactions. The memo field
you see in double-line mode is the one associated with the split in
the current account you are viewing. When you switch to the other
account you see the other memo field.

The next version of gnucash will have a transaction 'notes' field
that is the same no matter which account you open. Splits will
still have memo fields, but you will only see them in multi-line
mode.

dave