I'm beginning to wish I hadn't made that "helpful" initial post. What a lot
of heat over how things are said.
I'm not copying the earlier postings because I don't want to further inflame
this conversation.
The essential point is that the default that exists is (I assume without even
trying to check the code) a true default - the result of not putting any
code in for the default. The drop-down simply shows the first item on its
list. This means that any change is likely to be, in one sense, "bloat".
Now, the present arrangement is, in fact, very flexible. Each drop-down gets
its list from the user's settings when creating the list of accounts. So you
could take one of the following strategies:
1 - my strategy: use a single catch-all account with a prominent name
and set it to appear in all drop-downs.
2 - set a separate catch-all account for each type of drop-down (payable,
receivable, etc.) with a suitable name.
3 - select the account you would prefer to be the default for each type
of drop-down, and go to the chart of accounts and change each one's
number so that it is the first (numerically) amongst the accounts
with the coresponding 'include in drop-down menus' link. That
ensures you get the default you want.
This seems to me to be a pretty flexible arrangement. It obviously would not
be a huge effort or a great deal of code to put blank boxes up, but that
would altready be _less_ flexible for user configuration. I guess that doing
so would result in an error every time one was left blank, so no code would
be needed to prevent posting without a selection. To give user-configured
defaults chosen other than by sequence, must add to the code, comlexity and
configuration file size. Probably not by much, but bloat is often just the
accumulation of many little things - a bit like my overdraft.
I, personally, would vote for no change, but a more detailed user manual with
advice on issues like this. I like the leanness and speed of sql-ledger.
The additions to code that I seek are where no neat system is available for
managing repeated tasks. [for what it's worth, my current top three are
these:
- the addition of a boolean 'reconciled' to acc_trans and a routine to
carry out reconciliation against, for example, bank statements.
- the addition of account balance column to reports including the correct
initial balance where the printout is time limited.
- a script to spawn a copy of the datbase at year end, pre-seeded with
the opening balances from the previous year.]
--
richard
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
-------------------------------------------------------
(un)subscribe: http://lists.sourceforge.net/lists/listinfo/sql-ledger-users
Archive: http://www.mail-archive.com/[email protected]/
