rebalancing

[Conrad Canterford]

Dave Peticolas wrote:
> Proposal
> --------
> 1. Rebalancing should work by computing the imbalance, and then
>    modifying a specially designated 'imbalance' split to bring
>    the transaction into balance. If the imbalance split does not
>    exist one will be created. If it does exist and its value
>    should be zero for balance, the imbalance split will be
>    deleted.

I like this idea.

> 2. Rebalancing should only occur when user code requests it, not
>    automatically. For convenience, the xaccTransCommitEdit() api
>    should be extended with a flag to ask for rebalancing, but
>    user code can elect not to rebalance.

Can we have a user preferences option to always rebalance? (Ideally,
this should be possible on a per-register basis, but I'm not sure if
that is possible on the current arrangement).

> 3. The gui should visually identify imbalance splits, and allow
>    the user to bring up a list of unbalanced transactions.

Any thought on how this would be achieved? Are we talking an extra field
in the register, or some other arrangement (colour perhaps?).
On a vaguely related note, is it going to be possible to choose which
fields are visible in the register? I occurs to me that I never use the
"reconciled" field (or the action and memo fields, for that matter
although they are more problematical). Would tidy up my register view if
I could select to have it "hidden" on my register view. Of course,
you're now going to tell me that we can do that already....

Conrad.
-- 
Conrad Canterford (conrad@mail.watersprite.com.au)
Water Sprite Pty Ltd   | info@mail.watersprite.com.au
 GPO Box 355,          | Incorporating:
 Canberra, ACT, 2601   |   Australian Tour and Event Management (ATEM)
 Australia.            |   Ticketing Services Division
Phone: 0419 122 553    |   Catering Services Division