Group header replicated on each new page
Brought to you by:
a1s
Currently the group title element is only printed once, at the top of the group. If the group is split across a page or column break, it should be possible to optionally reproduce the title on the new page (or column).
Maybe this could be done by allowing the <header> element to be used within a group.
Also it would be useful to be able to determine inside the header if it is the first or a subsequent group header, so that some indication of continuation can be printed. (eg a field to print continued using a 'printwhen' style to disable it on the first header, at the top of the group).
Logged In: YES
user_id=8719
Originator: NO
page and column headings are meant to be fully described by the 'header' elements.
you can use <group>_COUNT variable to conditionally skip parts of the header in the middle of a group.
i am closing this request now. if the above technique does not work for you, please reopen the issue with example (data and template) demonstrating your problem.
Logged In: YES
user_id=784165
Originator: YES
Ok, thanks. That solution works, and my only gripe now is that I have to duplicate fields in the page header that are already in the group title, but I can live with that.
Logged In: YES
user_id=8719
Originator: NO
i think the following could work:
each element in report template gets an optional attribute 'id'. all non-empty ids must be unique across the template. (this is required by FR 1611603 also.)
new element type is added to all section elements: <link target="whatever">, where the 'target' attribute refers to existing id of another template element (section element or body element).
the 'link' element may contain one 'box' element, overriding the target box, and a sequence of 'style' elements, combined with the target styles (preceding them). if link target is a section, it's eject specifications are ignored.
PythonReports builder in it's constructor makes a private copy of the template, and unrolls all links by copying their targets in place. during this operation we should check for autorecursion.
perhaps the Section class will need to be modified to allow embedded sections.
patches are welcome.