Created attachment 80250 [details] (ignore this) Draw docs have a "canvas" (my term) which is much larger than the page size configured under Format->Page. For example, with an 8½ x 11" page, the "canvas" extends from approximately negative 9" to positive 16½". There does not seem to be any way to control the size of this "extra" space around the page. While editing a drawing this is sometimes merely inconvenient. However it is fatally problematic when importing a draw doc as an OLE object into, say, a calc spreadsheet because the "extra" space is part of the immutable opaque object, and so the drawing is pushed way off to the right when presented in the embedding document. Attached are two files "spreadsheet.ods" and "drawing.odg". The spreadsheet imports the drawing as an OLE object into a cell. Even though the drawing contains only a single small rectangle, the OLE object is huge in the spreadsheet and there is no way to place the drawing in the center of the cell (or even entirely on the page). Okay, at least I couldn't find a way. ==> It seems to me that either: 1. The "canvas" size should be configurable in Draw documents, so it can be made as small as needed, e.g., just large enough for the drawing, so that importing the drawing as OLE produces a minimal-sized object; or 2. OLE import in spreadsheets (and presumably other kinds of documents) should allow positioning the object partially off-page, so that the extra space can be put where it does no harm. Steps to reproduce: 1. Download the attached "spreadsheet.ods" and "drawing.odg" 2. Open the spreadsheet (may have to delete and re-import the linked drawing). 3. Try to put the rectangle in the middle of the cell (you can't) Operating System: Ubuntu Version: 4.0.3.3 release
Created attachment 80251 [details] (ignore this)
Created attachment 80252 [details] Demo file: Download to /tmp/spreadsheet.ods
Created attachment 80253 [details] Demo file: Download to /tmp/drawing.odg (to make the link work)
Thank you for reporting this issue! I have been able to confirm the issue on: Version: 4.2.0.0.alpha0+Build ID: b0a1666f756aa5f5315366eca9d7d02ddd55d2b Date: Tue May 28 08:51:01 2013 +0300 Platform: Bodhi Linux 2.2 x64 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + As I've been able to confirm this problem I am marking as: New (confirmed) Normal - can prevent high quality/professional work Low - honestly just not sure how many people this impacts. The test case shows the problem but it's not a real life test case as you can just copy/paste the actual rectangle from the drawing and paste into spreadsheet without issues - it only occurs if you want to do the entire drawing as OLE which IMHO seems rare (perhaps wrong though) Personally I think option 1 seems best - being able to edit the "canvas" size seems like it would have other benefits as well, the default is huge and obviously at least has one side effect + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage and join us on freenode at #libreoffice-qa There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
** 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 (4.4.1 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-03-16
Reproduced the bug using daily 4.4.2.0.0+ Build ID: ce8aba4da2a287c2b51d1d34a290284b2f754dc2), similar to Joel. I also noticed a nasty problem where if you double-click the linked image to enter edit mode, LO locks up with the screen corrupted. To get really exciting corruption, move the editable object around a little bit with the mouse. Please see attached screenshot.
Created attachment 114143 [details] Screenshot showing corruption after trying to edit linked drawing
Adding another confirmation of this issue, with LO 4.3.3.2 on Debian Jessie. I have a moderately complex block diagram which I am editing and storing in a separate .odg file, for ease of manipulation. This is then OLE embedded into the .odt document that it relates to. I would have preferred to keep it easily editable via OLE rather than having to generate and update a statically embedded copy. Unfortunately due to the oversized canvas, there are several centimetres of white space around the diagram, which is squeezed into the centre of the page in the outer, containing, document. I haven't been able to find a way around this that keeps the diagram editable via OLE. The best I can do is to stretch the embedded object over the entire width of the page, so the excess canvas coincides with the page margins. But this still somewhat wasteful of space and makes it hard to produce a high quality document.
Confirmed with LO 4.3.7.2 on RHEL 7.2. For me, this issue is very annoying since I work with large presentations containing tens of images that I do not want to embed by copy/pasting. The only workaround I am left with is to export from Draw into EMF and then insert as linked image in Impress.
And still the same on LO 5.0.5 :-(
** 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 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
Still no solution in 6.0 Version: 6.0.1.0.0+ Build ID: eba4d3b5a0667185e5a51a6e9996efbdbb51435d CPU threads: 12; OS: Linux 4.13; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:libreoffice-6-0, Time: 2018-01-31_23:34:32 Locale: en-US (en_US.UTF-8); Calc: group
Dear Jim Avera, 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
Problem still there in master as of Sept. 3, 2019 ersion: 6.4.0.0.alpha0+ Build ID: 4a63d78ded7b11c7b820d2c941a0c9aed18326fc CPU threads: 12; OS: Linux 5.0; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-09-03_04:42:45 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Dear Jim Avera, 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://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 Jim Avera, 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
(In reply to QA Administrators from comment #16) > Dear Jim Avera, > > 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. > > (…) Not Jim, yet I've just encountered this problem. About information Version: 24.2.5.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 12; OS: Linux 6.8; UI render: default; VCL: kf5 (cairo+xcb) Locale: pl-PL (C.UTF-8); UI: en-US Ubuntu package version: 4:24.2.5-0ubuntu0.24.04.2 Calc: threaded