https://bugs.kde.org/show_bug.cgi?id=307637
Holger <h.kl...@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |h.kl...@gmx.de
--- Comment #12 from Holger <h.kl...@gmx.de> ---
May I ask, why you opt for these uneven numbers ... 71 is a prime number, so
it'll guarantee distortion to most pictures. Yes, cubic algorithms do a
wonderful job on photos, so nobody will notice. But charts and other graphics
with straight lines still suffer.
I suggest rounding to nearby easy rational numbers:
x sqrt(2)^x rational value error
------------------------------------
-8 0,06 1/20 0,05 20,00%
-7 0,09 1/10 0,10 -13,14%
-6 0,13 3/20 0,15 -20,00%
-5 0,18 1/5 0,20 -13,14%
-4 0,25 1/4 0,25 0,00%
-3 0,35 1/3 0,33 5,72%
-2 0,50 1/2 0,50 0,00%
-1 0,71 3/4 0,75 -6,07%
0 1,00 1/1 1,00 0,00%
1 1,41 3/2 1,50 -6,07%
2 2,00 2/1 2,00 0,00%
3 2,83 3/1 3,00 -6,07%
4 4,00 4/1 4,00 0,00%
5 5,66 6/1 6,00 -6,07%
6 8,00 8/1 8,00 0,00%
7 11,31 11/1 11,00 2,77%
8 16,00 16/1 16,00 0,00%
The implementation could use a little lookup table for those values and compute
sqrt(2)^x only if out of range, though I expect the zoom increment only really
rarely exceeding the lookup range. But feel free to add more.
--
You are receiving this mail because:
You are watching all bug changes.
