Description: so, I try to make a project on Impress, and I can't move shapes out of the border! This inhibits the cretion of the project. Can you please fix it? Steps to Reproduce: 1. Grab a shape 2. Move it far from the slide Actual Results: The shape didn't go as far as I wanted it to. Expected Results: It should go as far as I want it to go. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.3 / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
It's possible to go outside the border for me (on Windows)
Works fine for me to move shapes outside the slide with gtk3. Is this happening with any fresh file? Btw., bad idea to use a temporary mailbox for your account. Arch Linux 64-bit Version: 7.1.0.3 / LibreOffice Community Build ID: 10(Build:3) CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US 7.1.0-1 Calc: threaded
(In reply to Buovjaga from comment #2) > Works fine for me to move shapes outside the slide with gtk3. Is this > happening with any fresh file? > > Btw., bad idea to use a temporary mailbox for your account. I assume it's being tracked.. Poster throw me out and reverted the title change. Didn't find the 'This is annoying!" of any (functional) value
The working area is limited to one slide width left and one slide width right, and to half slide height top and half slide height bottom. At least the extension in vertical direction needs to be larger. For example you are not able to use a motion path from bottom to top, so that an image with slide height is not visible at beginning. [I thought there is a bug report about this, but I cannot find it.]
Ok, I thought only I (btw, I'm using a permanent email now) could change the title and other stuff, so I kicked that person because I thought they were hacking.
Fair enough, let's adjust summary per Regina's observation.
*** Bug 144897 has been marked as a duplicate of this bug. ***