Dave Peticolas <[EMAIL PROTECTED]> writes:
> One fix would be to use a tree instead of just a list, but that
> would involve a lot of changes, as we would need a new register tree
> cell.
>
> Another would be to use fully-qualified account names, i.e.,
> Expense:BankOne Credit Card:Interest. This would not be foolproof,
> as you could still have duplicate accounts, although that would be
> much rarer. Also, account names might use the separator, which
> complicates things.
I still want to be able to just type in the account names (preferrably
with eventual tab completion). As I think I mentioned before, to do
this right, we need to agree on a textual "heirarchy separator", say
the colon ":", and then the user can use that to specify sub-accounts
-- as you indicated, you' have something like "Bank:Charges".
To handle the potential (though rare) case where there is a true
unresolvable ambiguity (i.e. someone uses ":" in an account name like
"Bank:Charges" when there is actually a matching heirarchy
element[1]), we can just allow escaping like this:
Bank:Charges -> specifies the Charges child account of Bank.
Bank\:Charges -> specifies an account named "Bank:Charges".
[1] In fact this will bite me for a while (until I go through and
rename my accounts). During the long migration from quicken -> cbb ->
gnucash, my heirarchy was flattened via colons.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
