Outline and childbands
Hi all.
I'm experiencing a issue using 'report outline' in combination with child-bands. Attached there are 2 simple reports (made-up to illustrate the problem). The first one have a group header with at child band attached. The second one has just the group header. If you test-run the reports they look almost the same, but there is a difference when clicking in the report outline:
The one without child band acts like expected, positioning the preview at the top of the group band from where the outline origins.
The one with a child band attached to the group header calculates the positioning wrong, and returns a postition just above the start of the details, or more accurate; it is (Groupheader1.height) above the details. It looks like the child band is forgotten in the positioning when clicking in the outline. So, when using the outline, you do not get a verification of acutally hitting the correct position unless you scroll up to se the 'hidden' group header and its child.
Is this a bug, or something I'm doing wrong?
Petter
I'm experiencing a issue using 'report outline' in combination with child-bands. Attached there are 2 simple reports (made-up to illustrate the problem). The first one have a group header with at child band attached. The second one has just the group header. If you test-run the reports they look almost the same, but there is a difference when clicking in the report outline:
The one without child band acts like expected, positioning the preview at the top of the group band from where the outline origins.
The one with a child band attached to the group header calculates the positioning wrong, and returns a postition just above the start of the details, or more accurate; it is (Groupheader1.height) above the details. It looks like the child band is forgotten in the positioning when clicking in the outline. So, when using the outline, you do not get a verification of acutally hitting the correct position unless you scroll up to se the 'hidden' group header and its child.
Is this a bug, or something I'm doing wrong?
Petter
Comments