Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


i just checked the zoom flow using debug.
The zoom action goes through the ViewOptions class
http://opengrok.libreoffice.org/xref/core/sw/inc/viewopt.hxx#163
it appears zoom is stored in nZoom, which is a
sal_uInt16<http://opengrok.libreoffice.org/s?defs=sal_uInt16&project=core>
  representing percentage.

So according to what you say, threre should be a different accessible
object or struct that holds the zoom with finer precision.
If so, then what object or class holds "the absolute source of truth" for
data regarding VCL elements?


On Mon, Aug 12, 2013 at 11:34 PM, Thorsten Behrens <
thb@documentfoundation.org> wrote:

Ptyl Dragon wrote:
We cannot express the difference between 1023 and 1024, in units of 1%,
as
1% of 1024 is 10.24. So the scale is not sufficient, and even if we fixed
it for iPad, tomorrow there might be a touch device with twice the
resolution.

Hi Ptyl,

yes, sure. But vcl itself uses integer fractions to express scaling
(check the MapMode class there), as such it should be able to convey
the necessary information. Thus the question for code to look at - I
seem to miss the point. ;)

Cheers,

-- Thorsten




-- 

[image: appicon.png]


*Ptyl Dragon*

Twitter <http://www.twitter.com/cloudoninc> |
LinkedIn<http://www.linkedin.com/company/cloudon>
 | Facebook <http://www.facebook.com/cloudoninc> |
Blog<http://site.cloudon.com/blog>

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.