Re: Problems with SetSnapRect() for rotated and/or sheared custom shapes

Miklos Vajna <vmiklos -AT- collabora.com>
Tue, 5 Nov 2019 08:50:12 +0100

Hi Regina,

On Mon, Nov 04, 2019 at 07:00:18PM +0100, Regina Henschel <rb.henschel@t-online.de> wrote:

So my question is:
What is SdrObjCustomShape::SetSnapRect() supposed to do?


My guess is the snap rectangle is the same as the bounding box, i.e. if
you have a shape with e.g. 45 deg rotation, the snap rectangle is larger
than the original size of the rectangle.

A different approach would be, to keep the current version of
SdrObjCustomShape::SetSnapRect() and change the found combinations so, that
in case of a SdrObjCustomShape, not GetSnapRect() but GetLogicRect() is
used.


Do we know what "logic" means in GetLogicRect()? Is that "logic" because
it's in mm100/twips, not pixels or something else?

Regards,

Miklos

Attachment: signature.asc
Description: Digital signature

Context

Problems with SetSnapRect() for rotated and/or sheared custom shapes · Regina Henschel
- Re: Problems with SetSnapRect() for rotated and/or sheared custom shapes · Miklos Vajna
  - Re: Problems with SetSnapRect() for rotated and/or sheared custom shapes · Regina Henschel
    - Re: Problems with SetSnapRect() for rotated and/or sheared custom shapes · Regina Henschel
      - Re: Problems with SetSnapRect() for rotated and/or sheared custom shapes · Thorsten Behrens
- Re: Problems with SetSnapRect() for rotated and/or sheared custom shapes · Regina Henschel

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.