The issue reported in bug 78413 persists for any other shapes (looks like it has been fixed for rectangle only). - draw a shape (other than rectangle) - select it - ctrl+c - ctrl-v (the copied object becomes selected) - check position and size (both position coordinates are at 0.01 offset) Trying the daily build (libo-43~2014-09-16_08.54.36_LibreOfficeDev_4.3.3.0.0_Win_x86.msi) and the reported bahavior is not reproducible. Might this depend on any settings?
Created attachment 106981 [details] ODG with various shapes LOv4322 (In reply to comment #0) > Might this depend on any settings? The various snap-to-grid options would likely be influential. You will need to ensure these are turned off before testing. (In reply to comment #0) > - check position and size (both position coordinates are at 0.01 offset) Please indicate the units being used. Unable to reproduce under GNU/Linux using v4.3.2.2 in the attached example, for the default centimetre unit.
As a result of comment 1, status set to NEEDINFO. Please set back to UNCONFIRMED once the requested information is provided. Thanks.
- Using millimeters as the main units, but centimeters behave the same. - Testing snap to grid and grid granularity, no influence on the offset. Opening the attached "ODG with various shapes LOv4322" in OO 4.4.1.1 on Win7 64 bit and using following steps: - select (click) the shape, - ctrl-c, - ctrl-v, - check the position of the pasted one (expecting the exact same position and size as the original) 1) Rectangle: *same as the original* 2) Circle : x+0.01 mm, y+0.01 mm 3) Cylinder : x+0.01 mm, y+0.01 mm 4) Heart : x+0.01 mm (y unchanged!) 5) LArrow : x+0.01 mm, y+0.01 mm 6) Flag : x+0.01 mm, y+0.01 mm 7) Bubble : x+0.01 mm, y+5.43 mm (WTF?) 8) Star : x+0.01 mm, y+0.01 mm 9) RArrow : *same as the original*
As this is pretty annoying I have performed following additional steps: 1) Complete wipe of ANY libre/open office traces in system (uninstall, delete program/data directories) 2) Clean instal of LO 4.4.1.1 (msi downloaded from http://dev-builds.libreoffice.org/pre-releases/win/x86/ 3) Testing of following shapes in default setup is OK: - rectangle, - ellipse, - heart!. The bubble is weird even in the default setup, it adds 1.03cm to y coordinate. 4) Change settings from default to "my" values (due to localization I would try to guess the original english equivalents): - general, measurement units : centimeters -> millimeters - grid, main spacing (both) : 10.00mm -> 5.00mm - grid, aux spacing (both) : 10 -> 5 This is the setup the described copy/paste behaviour occurs. I'm starting to suspect the code of some wrongly handled floating point arithmetics and rounding problems... Could you please apply these details and try to reproduce?
Reproduced results from comment 3 on Win & Linux. Tools - Options - LibreOffice Draw - General - Unit of measurement: Millimeter In the sidebar, have Position and size visible to immediately see the change. This isn't major, though (can be correctec manually afterwards), so lowering severity: https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Win 7 Pro 64-bit, LibO Version: 4.4.0.3 Build ID: de093506bcdc5fafd9023ee680b8c60e3e0645d7 Locale: fi_FI Version: 4.5.0.0.alpha0+ Build ID: b13534de022972131b46f93f5ada90af155eec9e TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-02-19_00:21:37 Locale: fi_FI Ubuntu 14.10 64-bit Version: 4.4.0.3 Build ID: 40m0(Build:3) Locale: en_US
In LibreOffice 5.0.1.2, it is a pain when something pastes out of view, and you have to scroll around the document, find the object, and drag it back. For example, if I copy something at 3.7in x 2.9in, it may paste at 5.68in x 4.48 in.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Dear pafal, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear pafal, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug