QCustomPlot Discussion and Comments

bug report: off-by-one in getValueRange()Return to overview

getValueRange should not consider any elements with keys which are not contained in the inKeyRange

currently this is not the case because findEnd and findBegin are called with expandedRange=true

you may wonder what the big deal is - but actually if the data is sparse on the key range, and the value range is highly dynamic, then including one extra element will often totally screw up the result.

Thanks for the bugreport, dave! will be fixed in the next release.