Bug Hunting Session
Bug 45338 - EDITING ReportBuilder: 'Details - General Keep Together' without visible effect
Summary: EDITING ReportBuilder: 'Details - General Keep Together' without visible effect
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 79595 (view as bug list)
Depends on:
Blocks: Database-Reports-Builder-MAB
  Show dependency treegraph
 
Reported: 2012-01-28 08:10 UTC by Robert Großkopf
Modified: 2019-01-06 07:29 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
Pagebreak destroys cohesion of information in "detail" (29.46 KB, application/vnd.sun.xml.base)
2012-01-28 08:10 UTC, Robert Großkopf
Details
Better file, shows only with detail and allright with group without content (51.33 KB, application/vnd.sun.xml.base)
2012-01-28 10:30 UTC, Robert Großkopf
Details
Descripion for pagebreak in the area details with option "keep together". (63.92 KB, application/pdf)
2012-07-31 09:39 UTC, Robert Großkopf
Details
Compare results "With Keep Together" <-> "Without Keep Together" (19.17 KB, application/x-7z-compressed)
2012-08-06 09:18 UTC, Rainer Bielefeld Retired
Details
more minimal testcase (70.39 KB, application/vnd.oasis.opendocument.database)
2013-03-11 16:40 UTC, Lionel Elie Mamane
Details
Minimal testcase - added one report without shapes (75.91 KB, application/vnd.sun.xml.base)
2013-03-13 08:50 UTC, Robert Großkopf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Großkopf 2012-01-28 08:10:11 UTC
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.
Comment 1 Robert Großkopf 2012-01-28 10:30:42 UTC
Created attachment 56264 [details]
Better file, shows only with detail and allright with group without content
Comment 2 Robert Großkopf 2012-07-31 09:39:10 UTC
Created attachment 64986 [details]
Descripion for pagebreak in the area details with option "keep together".
Comment 3 Rainer Bielefeld Retired 2012-08-06 07:51:42 UTC
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 ..."?
Comment 4 Rainer Bielefeld Retired 2012-08-06 08:34:22 UTC
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
Comment 5 Rainer Bielefeld Retired 2012-08-06 09:18:24 UTC
Created attachment 65157 [details]
Compare results "With Keep Together" <-> "Without Keep Together"
Comment 6 Jochen 2012-08-06 09:44:06 UTC
(In reply to comment #5)
> Created attachment 65157 [details]
> Compare results "With Keep Together" <-> "Without Keep Together"

Hi Rainer,

no difference. Right?
Conclusion?
Comment 7 Rainer Bielefeld Retired 2012-08-06 09:53:15 UTC
> 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.
Comment 8 Lionel Elie Mamane 2013-03-11 16:40:12 UTC
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.
Comment 9 Lionel Elie Mamane 2013-03-11 17:20:35 UTC
(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...
Comment 10 Robert Großkopf 2013-03-13 08:50:03 UTC
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.
Comment 11 Robert Großkopf 2013-03-13 08:56:13 UTC
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.
Comment 12 Robert Großkopf 2013-08-07 14:31:13 UTC
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.
Comment 13 Dominik 2014-06-03 17:20:04 UTC
*** Bug 79595 has been marked as a duplicate of this bug. ***
Comment 14 Alex Thurgood 2015-01-03 17:40:33 UTC Comment hidden (no-value)
Comment 15 QA Administrators 2016-01-17 20:03:16 UTC Comment hidden (obsolete)
Comment 16 Robert Großkopf 2016-01-27 17:52:44 UTC
Bug still exists with LO 5.1.0.2, OpenSUSE 42.1 Leap, 64bit rpm Linux.
Comment 17 Robert Großkopf 2016-03-06 08:23:53 UTC
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".
Comment 18 QA Administrators 2017-03-06 15:23:14 UTC Comment hidden (obsolete)
Comment 19 Robert Großkopf 2017-03-07 16:21:54 UTC
Bug still exists with LO 5.3.1.1, OpenSUSE 42.1 Leap, 64bit rpm Linux.
Comment 20 f.rr 2017-03-08 22:59:59 UTC
The bug is still present in Version: 5.2.6.2 on Fedora 25, 64 bit (Gnome)
Comment 21 Howard Johnson 2018-01-05 06:13:46 UTC
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
Comment 22 QA Administrators 2019-01-06 04:19:48 UTC Comment hidden (obsolete)
Comment 23 Robert Großkopf 2019-01-06 07:29:05 UTC
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)