Hi Markus,
Many thanks for looking into this, I know the code for these program indicators
is complex! Will this be fixed in a future release? (I realise it’s probably
not a high priority for 2.25 if there’s a known workaround.)
And many thanks for clarifying that I now need to specify a
Hi there Sam,
thank you for the detailed report.
The division is done with integers when both the inputs are integers. So the
result of the divison is rounded down from f.ex. 0,66 to 0 before the
multiplication with 100 happens. You found a workaround yourself, another
option would be to do
Hi all,
Just following up on this bug report again – is there any chance I could get it
looked at/prioritized?
I’ve dug a little deeper, and it looks like this bug could be as simple as an
error in variable handling.
Specifically, although in the example I originally gave, the following
Hi all,
I reported a bug in the web program indicator calculations a couple of weeks
ago, and included in the report everything that’s needed to quickly replicate
the bug, but I don’t think anyone has had a chance to look at this report yet.
Have I followed the correct process for reporting
Public bug reported:
Bug found in 2.22, still present in 2.24 online demo (2.24 rev.23557)
Online demo accessed using Chrome 52.0.2743.116.
There appears to be a bug in the program indicator calculations when:
a sum() custom aggregation is used twice, to enable the calculation of a
percentage
5 matches
Mail list logo
