Rounding in the price db.

[David Carlson]

Oh, I completely forgot to mention that the new documentation page is much
better.  Sorry about forgetting to mention that.

David C

On Tue, Sep 22, 2015 at 8:59 AM, David Carlson <david.carlson.417 at gmail.com>
wrote:

> Testing git rev 766cf48+ on 2015-09-18, I have a report using "Nearest in
> Time" price reference.  There is an F::Q price for January 30 2015 in the
> db and a user:split-register price has now appeared for February 1 that is
> slightly off because the transaction that generated it was for 2.203 shares
> at $10.16 totalling $22.38.  That translates to 10.158874 per share in
> GnuCash.  Now my January 31 2015 report is off by $0.67 for that security
> and also for a couple of other securities with the same issue.  Last
> January the report was correct.  I know that there has been discussion
> about having a report option that would not select following-day prices and
> here is the example of why I think it is needed.  This year is bad that
> way, February May and October present the same situation.  Going back and
> adding a lot of bogus weekend prices just to get good reports would be a
> pain.
>
> By the way, when I went into the price db to add a price for January 31, I
> noticed that the February 1 price was labelled as unknown type and no
> source was shown in the edit window, just in the list.  I thought the
> source used to be shown in the edit window as well.  That is not a real
> issue, but when I edited the February 1 price to 10.16 the source was not
> changed to user: price-editor as it should have been.
> Also, I happened to be sitting on February 1 when I selected Add new
> price.  I put the focus on the date in the editor window and pressed the
> minus key the date changed to January 30.  Pressing the plus key then
> correctly advanced the date to January 31.
> I hope those are the only issues.
>
> David C
>
> On Sun, Sep 20, 2015 at 3:58 PM, John Ralls <jralls at ceridwen.us> wrote:
>
>>
>> > On Sep 20, 2015, at 6:35 AM, David Carlson <david.carlson.417 at gmail.com>
>> wrote:
>> >
>> > By hard to read, I mainly mean that the new section 6.2 now contains
>> four note bullets that at least appear to be warnings about exceptions or
>> special cases or something.  The first one starts out with "The following
>> sections will..." but it isn't clear where that reference ends.  Maybe it
>> and the parts that it references should be indented or in a box or
>> delimited by some sort of paragraph or topic separator icon.  If it only
>> applies to the three numbered sentences, then changing it to read "The
>> following numbered sections will..." would likely suffice.
>> >
>> >  I really did not want to make specific suggestions until I could
>> understand why each sentence is there and how they fit together.  I have
>> not reached that point, so my suggestions may not even work.
>> >
>> > Is it possible to have the page clearly divided into a section that
>> describes what it is intended to do followed by a section of details how to
>> use it?
>> >
>>
>> Sure is, and I’ve done it. It will be in the documentation nightlies (
>> http://www.gnucash.org/viewdoc.phtml?rev=trunk&lang=C&doc=help) tomorrow
>> morning.
>>
>> Regards,
>> John Ralls
>>
>>
>>
>