Transfer window appears when it should not - further information

[Ken Heard]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2015-02-17 13:16, I wrote:

> On occasion, when I need to change amounts in a split transaction 
> GnuCash will not let me change one or more of them.  Instead the 
> transfer window appears and wants me to enter exchange rate
> information.
> 
> Since whenever this situation arises -- seemingly at random -- all
> of the accounts are in the same currency; consequently there is no
> need to enter exchange information.  However GnuCash will not let
> me make the changes I need to make unless I do enter exchange
> information.
> 
> I tried closing GnuCash and opening it again, but it made no 
> difference.  I am using GnuCash 2.6.4 with Debian Wheezy.
> 
> 
> How do I stop this situation from occurring?

Since I wrote the above I have further information as to what
happened.  Originally all the entries in the transaction were in
Canadian dollars.  I needed to change one of the amounts.  After I
changed it the difference was assigned to an imbalance account.

I expected the imbalance to be in account Imbalance-CAD, but it was
assigned to account Imbalance-THB instead.  Why I cannot imagine.
Although I am presently in Thailand, all the accounts used in the
transaction were in CAD.  It would consequently make sense to me that
GnuCash would use the CAD imbalance account instead of the THB one,
specifically the currency of the account anchoring the transation.

When I discovered this error I changed the imbalance account to CAD
from THB.  Nevertheless, GnuCash *still* opened the transfer window
and asked for a CAD-THB rate -- or enter an amount I would choose for
the other currency and let GnuCash calculate the rate.  I tried once
again to close and open again GnuCash to no effect.

Furthermore, I discovered the same phenomenon happens in other
transactions once having an account in a currency different from the
currency of the account anchoring the transaction, but which had since
been removed.

I am unsure as to how to stop this phenomenon. Can be stopped, or is
it simply a bug?

Regards, Ken Heard


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlTi+N0ACgkQlNlJzOkJmTeq4QCfQ3G5x9RRJD+VPmQ8RT7e3fwf
FE0AnR1jdPU0U/g7ph/gkN2BrOQ9bKnf
=iuXA
-----END PGP SIGNATURE-----