[GNC-dev] Transaction / Split Action List
geert.gnucash at kobaltwit.be
Sat Jun 23 12:14:48 EDT 2018
Op zaterdag 23 juni 2018 18:12:34 CEST schreef John Ralls:
> > On Jun 23, 2018, at 4:58 AM, Robert Fewell <14ubobit at gmail.com> wrote:
> > There have been some enquiries about customising this list so I thought I
> > would propose a possible solution that I may work.
> > At the moment the static lists are based on register type in
> > split-register.c and it looks to me there are two possible options.
> > 1, Dynamicaly add to these lists based on past entries, probably there
> > would be an overhead do so.
> > 2, Allow the lists to be customised in some sort of config file.
> > I think 2, is the better option and in the source it mentions about using
> > a
> > config file so I was thinking along those lines to basicly do...
> > Create a new user key file probably in .config/gnucash called
> > user-config.gcm
> > On gnucash load, test for the file and if not present create it with the
> > default list content of split-register.c, I assume this would populate the
> > file with the translated entries.
> > A section name would then have list keys for the entries, something
> > like...
> > [Action List]
> > cash_register=Increase;Decrease;Buy;Sell
> > asset_register=Buy;Sell;Fee
> > Change gnc_split_register_config_action to read the key file content to
> > populate the appropriate list.
> > A missing register key would get a list of one entry with "Empty".
> > This would allow the users, once the file is created to add or remove
> > entries as required.
> > Any thoughts, wrong approach ?
> > This would probably be a master project.
> User-edited “ini” files are so 1980s. Anything like this should have a GUI
> I suspect at least some users would want to be able to set this per-account,
> but I think it more important to find out how many care at all and where it
> fits in most users’ list of priorities for improvements. It might even be
> that most users prefer the current pre-populated combo box that allows them
> to put anything they like in there, or that most don’t even use it.
> John Ralls
Agreed. I propose someone that cares to put up a feature request on userbase
and invite others to vote on it. That should give some indication of perceived
More information about the gnucash-devel