On 03/03/2018 17:59, Geert Janssens wrote:
Op zaterdag 3 maart 2018 16:35:27 CET schreef David Carlson:
On January 30, 2015 I reported
https://bugzilla.gnome.org/show_bug.cgi?id=743753 pointing out this
behavior in Gnucash suggesting that the nearest in time criterion should
not select future dates. That bug report applied to release 2.6.5 and as
of today it still has a status of "New" If this criterion with it's
current behavior is the desired behavior, I assert that there should be
another criterion "last price on or before" so users can make their GnuCash
year end reports match their brokers statements without fudging prices in
their data files.
I think having the extra option would be useful and less confusing than having
"Nearest in time" only look backwards.
Geert
Ummm, Geert, he's talking about a conversation from 2015
The "Nearest in time" as a sensible price default happened *after* that.
Further, as far as I know, if I want a future price for any commodity I
have to pay for it.
How can we, ordinary people, be getting these future prices in the first
place?
Do other people not realise how much a future price can be worth? We
are talking millions of USD, GBP or EUR and that could be millions less
or more than you currently have.
===
You're also being lazy wrt your tax reports and I reckon once you've
done them you'll want "Nearest in time" to mean what it says and you'll
realise you've been lazy setting your period dates (I do that too).
--
Wm
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
