Yes, I know how it works - BBox doesn't cut the image, but shows the part of it through something like window or viewport, the zoom mode just calculates and sets the zoom level, and we can pan (move) the image to the right or to the left relative to viewport. But if the left margin can be set in the "Fit to content" / "content height" modes, why the right can't? The grey fields
should be slightly more, whilst the right white margin - slightly less, and the
content set with BBox should be centered.
The content itself, not the content plus all the right margin to the page edge. I think.
Using of the "Fit to content width" gives us the more zoom and more comfortable reading, but the page can be shown not the whole - if it is tall and narrow - and the tiny part of it is hidden on the next screen. In comics mode it's hard to realise where the current line of reading is. If we read text, of course, not staring on pictures. The overlap shading doesn't help at all - this function is very buggy. That's why in this case (when the second part of page is really tiny) it's better to use fitting to content / content height. And it's all OK, but the fact that the content is not centered bothers me a little bit. I'm an perfectionist, you see.
The setting of grey background to white color is not our way. I see into the code and try to understand how it works. Offset_x and offset_y set the grey fields - I know, but I'm not sure how work pan_x, _y, _x1, _y1 and in which place of code they are set. Setting the different values of them in corresponding section of setzoom() does not make the visual difference, so probably they're really set somewhere else. "offset_" does, but not "pan_"
