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


Hi Thorsten,

Thanks for your reply.

Thorsten Behrens wrote:
tools::Point is not exactly a role model for a nicely designed class,
so I'd hesitate to take any literal bits out of that. ;)

Good to know, I'm new to the codebase so I'll keep that in mind.


Many places using AdjustX() also call AdjustY() just the next line, so
for that you could use basegfx::B2DPoint::operator+=(const B2DTuple&)

Sure but there are occasions in the code where we are just modifying
a single coordinate. My recent patch is an example:
https://gerrit.libreoffice.org/#/c/70329/ <https://gerrit.libreoffice.org/#/c/70329/>


If you believe you *must* use a single-component modifier

A single-component modifier isn't a must but it might be nice for
when we are only changing one coordinate.


please come up with something that blends well with the b2dtuple/point
concept. Also ideally, you will maintain some amount of internal
consistency (e.g. compare how operator*, *= etc. all got added in
farious flavours, such that math with b2dtuples works like the
'canonical' way when done with skalars or various forms of vectors).

If we do decide to go ahead with this I'll be sure to follow your
implementation requirements.

With many thanks,
Alex

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.