https://bugs.kde.org/show_bug.cgi?id=249364
--- Comment #2 from Thomas Fischer <fischer unix-ag uni-kl de> 2010-09-04 11:22:14 --- > Is that 1.25 supposed to be the aspectRatio of the users screen? No, not directly. The patch first computes the aspect ratios of the page and the aspect ratio of the space available to display the page (as determined by rowHeight and colWidth). Then both aspect ratios are compared by dividing one with another, the result is stored in variable rel. If both aspect ratios are very similar, such as when viewing presentations in a full-screen okular on a 3:4 or 16:9 monitor, rel is somewhere around 1 and the best zoom option would be "fit page" (third case in the following if block). Now, this "very similar" has to be put in a numeric value and this is aspectRatioRelation. Having a value of 1.25, it states that if 0.8<rel<1.25 holds, best "fit page" is the best zoom option. If rel is below 0.8, the page to view is relatively higher than the available space and "fit width" is most appropriate to utilize the space best. "Fit page" would render any text on the page unreadable (assuming I would open an A4 page/portrait with normal 10-12pt text). The same principle holds for rel >1.25 resulting in a "fit height" zoom. Another advantage with best fit is, that in the "page fit" case no scrolling is necessary and the mouse wheel allows to jump between pages (very useful for slide sets), and in the other two cases, only one scroll bar is used making browsing through the document much easier. I hope this explains the patch... -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel