Pushed, thanks!
Marek
On Fri, Jul 14, 2017 at 9:59 AM, Christoph Haag
wrote:
> The fps graph for example calculates the fps as double with small
> variations based on when query_new_value() is called, which causes
> many values to be truncated on the cast to uint64_t.
>
> The HUD internally stor
The fps graph for example calculates the fps as double with small
variations based on when query_new_value() is called, which causes
many values to be truncated on the cast to uint64_t.
The HUD internally stores the values as double, so just use double
everywhere instead of fixing this with roundi
