https://bugs.documentfoundation.org/show_bug.cgi?id=160856

V Stuart Foote <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected],
                   |                            |[email protected]
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW

--- Comment #2 from V Stuart Foote <[email protected]> ---
Confirmed. Transformation applied by page Orientation in the Print dialog
differs from transformation applied with page reorientation of document canvas.
Shape content does not track and is mispositioned in preview.

In Draw (not in the Print dialog) I did note that changing canvas from
Landscape to Portrait means the rotation/anchor for the shape will be in the
wrong position on the canvas. Trivial but necessary to adjust that, or object
will be mispositioned--when editing further. Not clear that a global anchor for
all objects on a Draw page can be defined, each is anchored/rotated
independently.

To demonstrate, attaching a version of attachment 193880 where I have set a
page size of 3.5" x 1.25" to match the Text box "label", and added a page with
the "label" rotated 270° -- such that using the Draw -> Page -> 'Page
Properties...' dialog radio button toggle the ODG between Landscape and
Portrait Orientation, one page or the other correct depending on the
orientation.

Then try the Print dialog preview with each, using the Print dialog's
Orientation list box (Automatic, Portrait, Landscape) note that the
transformation applied in the Print dialog does not match transformation of the
Draw canvas.

Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to