We have integrated LibreOffice in out Tool, and we are creating some Shapes programmatically in sdraw. After a few Shapes (more than 65535) the Shapes are not shown as expected (some are in Back or other, while they should be in Front). This is because the ZOrder of the Shapes are not incremented after 65535. I have wrote a Macro to reproduce it (see end of the Description) In LibreOffice 4.0.3.3 it is reproducible. I have tried to reproduce it in LibreOffice 5.0.0.5, but the program crashed after a couple of time and the macro will not finish. Macro: Dim shapeSize As new com.sun.star.awt.Size Dim shapePos As new com.sun.star.awt.Point Dim I Dim shape shapeSize.width = 2000 shapeSize.height = 3000 document = ThisComponent drawPage = document.DrawPages(0) For I = 1 To 65540 Step 1 shape = document.createInstance("com.sun.star.drawing.RectangleShape") drawPage.add(shape) 'shape.ZOrder = i shapePos.X = i shapePos.Y = i shape.setPosition(shapePos) shape.setSize(shapeSize) If shape.ZOrder > 65534 Then MsgBox shape.ZOrder End If Next I
Confirmed the weirdness in 5.0.1, but was unable to get a backtrace. Win 7 Pro 64-bit, Version: 5.0.1.2 (32-bit) Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Locale: fi-FI (fi_FI)
Part of backtrace: #0 SdrObject::GetOrdNum (this=0x89ca6f0) at /home/julien/lo/libreoffice/svx/source/svdraw/svdobj.cxx:777 #1 0x00002aaab0d950af in SvxShape::getPropertyValueImpl (this=0x89c8ff0, pProperty=0x4196350, rValue=uno::Any(void)) at /home/julien/lo/libreoffice/svx/source/unodraw/unoshape.cxx:2576 #2 0x00002aaab0d9d86a in SvxShapeText::getPropertyValueImpl (this=0x89c8ff0, rName="ZOrder", pProperty=0x4196350, rValue=uno::Any(void)) at /home/julien/lo/libreoffice/svx/source/unodraw/unoshape.cxx:4077 #3 0x00002aaab0d91dc8 in SvxShape::_getPropertyValue (this=0x89c8ff0, PropertyName="ZOrder") at /home/julien/lo/libreoffice/svx/source/unodraw/unoshape.cxx:1744 #4 0x00002aaad3f47292 in SdXShape::getPropertyValue (this=0x89a62b0, PropertyName="ZOrder") at /home/julien/lo/libreoffice/sd/source/ui/unoidl/unoobj.cxx:831 #5 0x00002aaab0d91c60 in SvxShape::getPropertyValue (this=0x89c8ff0, PropertyName="ZOrder") at /home/julien/lo/libreoffice/svx/source/unodraw/unoshape.cxx:1725 #6 0x00002aaaf23e66e3 in (anonymous namespace)::IntrospectionAccessStatic_Impl::getPropertyValueByIndex (this=0x83c8cf0, obj= uno::Any("com.sun.star.uno.XInterface": {_vptr.XInterface = 0x89c9028}), nSequenceIndex=40) at /home/julien/lo/libreoffice/stoc/source/inspect/introspection.cxx:571 I'm not sure but it seems to depend on SdrObjList::RecalcObjOrdNums() which depends on SdrObjList::GetObjCount() which corresponds to maList.size(); finally maList is defined as ListType which is typedef std::vector<std::unique_ptr<SdrObjUserData> > ListType; So might be system constraint.
Yes, a limitation due to the old roots of the office. Changed in aw080 (I think), but not yet available...
** 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.4.1 or 5.3.6 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-20170901
Dear mmaurer, 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
Bug is still present Version: 6.3.3.2 (x64) Build-ID: a64200df03143b798afd1ec74a12ab50359878ed CPU-Threads: 8; BS: Windows 10.0; UI-Render: GL; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded
Dear mmaurer, 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
I tried to reproduce this on pc Debian x86-64 with master sources updated today but either I missed something or it seems to work. Could someone give a try at least with LO 7.5.5 or with LO 7.6.0 ?
Yes, it works OK Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f5bcc34580d02f92af01963155f2d54776a5249b CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded