Created attachment 56260 [details] Pagebreak destroys cohesion of information in "detail" When I will make a report like a table I put the content in "detail". Then I whish data of one row will not put out on two pages. But this wont work. There is a button in the German version called "zusammenhalten" ("hold together" or "bind" - I do not know the button in English). But this chages nothing. It could be, that graphical elements of "detail" are at one page and the content of the data-row is on the other. Workaround today: Put all content in "group", nothing in "detail". The content is then ordered - could be not in that way, you want, but all is hold together on one page. When you open the report in the attachment you will know what I mean.
Created attachment 56264 [details] Better file, shows only with detail and allright with group without content
Created attachment 64986 [details] Descripion for pagebreak in the area details with option "keep together".
This bug has never been confirmed, so NEW is not correct Even Version is missing ... I will test this soon. @Reporter: Please read <https://www.libreoffice.org/get-help/bug/> what will help to create more useful bug reports. Is your first sample document obsolete? If yes, please mark so. Concerning "Keep together" I can't see any difference in properties of reports in "Better file ..."?
Might be related to .m. AOOo bug, what has been marked as DUP of a Bug from 2009, what is still unfixed. From "Pagebreak destroys cohesion" I created a report with "Keep Together" and without "keep together", view of created reports and Printouts (please see attached results as FreePDF prints" are equal, data set 19 will be spread on 2 pages. Even Worse: part 2 of the detail will be shown outside the 2 (blue and yellow) bars markint top and bottom of each detail, but that might be a different bug. Help is rather imprecise here (you can do some tuning ...) Already [Reproducible] with "LibreOffice 3.4.5 English UI [Build ID: OOO340m1 (Build:502)]" parallel Server installation on German WIN7 Home Premium (64bit), I believe that never worked. @Lionel: Please set Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug or forward the Bug if it's not your turf. @Robert: No further info required
Created attachment 65157 [details] Compare results "With Keep Together" <-> "Without Keep Together"
(In reply to comment #5) > Created attachment 65157 [details] > Compare results "With Keep Together" <-> "Without Keep Together" Hi Rainer, no difference. Right? Conclusion?
> no difference. Right? Yes, as per Comment 4, where Bugzilla ate my Attachment ;-) Lionel is already on CC, so currently no need for further action here.
Created attachment 76344 [details] more minimal testcase This testcase is a bit more minimal in its difference(s) between the two reports, for better clarity. In Robert's testcase, the two reports had DIFFERENT Detail section heights, which changes the whole layout and make comparisons moot. There are actually several "problems" visible here: 1) IMHO trailing (not leading) vertical blank space should be "eaten" by a pagebreak. This would make this particular testcase not trigger this bug in the same way, since each page would contain the same number of records. Looking closely at the execution result of the "detail_dont_hold_together" report, one sees that page 2 begins with the trailing blank space of detail section ID=9. That's a bit silly. If detail ID=9 fit into page 1 (except for its trailing blank space), the trailing blank space should just disappear, and page 2 should start with a new detail section (instead of trailing blank space that belongs to the previous detail section). Same holds for vertical blank space WITHIN a detail (or other) section: start the next control right at top of effective area of next page (effective area = after header, before footer), don't take over vertical blank space that did not "fit" in previous area. (You may notice that what I have in mind is the TeX/LaTeX behaviour.) THIS IS INDEPENDENT OF THE "keep together" setting. 2) If one looks closely at the result of the "detail_dont_hold_together" report, one actually sees that the yellow line below 9/Liesbeth OVERLAPS WITH THE FOOTER. That is made more clear by the report "Detail_dont_hold_together_footer". This also causes on page 2, the fact that the yellow line at bottom is on page 2, but the "Name Eike" on page 3. This looks like a Writer bug, actually. 3) In the generated result, the detailNN tables should have "Allow table to split across pages and columns" set to false, but don't. That's my understanding of what *this* bug is about.
(In reply to comment #8) > 2) If one looks closely at the result of the "detail_dont_hold_together" > report, one actually sees that the yellow line below 9/Liesbeth > OVERLAPS WITH THE FOOTER. That is made more clear by the report > "Detail_dont_hold_together_footer". > > This also causes on page 2, the fact that the yellow line at bottom is > on page 2, but the "Name Eike" on page 3. > > This looks like a Writer bug, actually. No, it is not as such a Writer bug. The ODT generated by reportbuilder puts *all* shape elements of the whole detail section in the *topmost* (first) row of the DetailNN table. It just happens to work because apparently rows are "allowed" to overlap in Writer. Whether this is guaranteed by the OpenDocument standard is another question entirely. This may be rather hard to fix while still allowing shapes to overlap with report controls like they now do. I'm not quite clear on whether it is important for them to be allowed to overlap...
Created attachment 76456 [details] Minimal testcase - added one report without shapes Have added a report to https://bugs.freedesktop.org/attachment.cgi?id=76344&action=edit without any shapes, without header and footer. Set "Detais" - "hold together". The section "details" won't be hold together. "Group" - "hold together" would work. This is the workaround many users would use.
Shapes have nothing to do with this bug-report. The bug appears also without shapes. All fields in a report couldn't overlap except shapes. This would be a good idea for changing backgrounds of fields, for setting frames around fields (remember: horizontal and vertical lines are not working at this moment in the Report-Builder). Let us have a look at this bug without shapes.
Just testing all bugs from Report-Builder. This bug first appears in the oldest available version of LO, 3.3.0 beta1. So I set the first available bugzilla-version, 3.3.0 release.
*** Bug 79595 has been marked as a duplicate of this bug. ***
Adding self to CC if not already on
** 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.0.4 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: 2016-01-17
Bug still exists with LO 5.1.0.2, OpenSUSE 42.1 Leap, 64bit rpm Linux.
Bug appears in the first available LO-version (LO 3.3.0.4, OpenSUSE 42.1 64bit rpm Linux). So I set this bug as "Inherited From OOo".
** 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.2.5 or 5.3.0 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-20170306
Bug still exists with LO 5.3.1.1, OpenSUSE 42.1 Leap, 64bit rpm Linux.
The bug is still present in Version: 5.2.6.2 on Fedora 25, 64 bit (Gnome)
Still seeing this bug. Debian 9.3, LO 5.4.3.2 Also some general confusion about `General` vs `Sorting and Grouping` `Keep Together`. See: https://ask.libreoffice.org/en/question/27689/keeping-data-together-in-libre-database-report/?answer=142288#post-id-142288
** 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
Bug still exists in LO 6.1.4.2, also in Version: 6.2.0.1 Build ID: 0412ee99e862f384c1106d0841a950c4cfaa9df1 CPU threads: 6; OS: Linux 4.12; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); UI-Language: en-US Calc: threaded (OpenSUSE 64bit rpm Linux)
Dear Robert Großkopf, 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
Almost the same behavior in LO 7.0.4.2 on OpenSUSE 15.2 64bit rpm Linux
Have had a new look on this bug. Detail-section won't be kept together, because 1) there will be created only one table "Detail0" when starting a report without grouping 2) the section will always been set tho allow table to split across pages. The first part will be changed by grouping the report ("Detail0", "Detail1" … will be created) Now I'm looking in the code for getting this behavior also for non-grouped reports …