This is likely a known issue, but just in case: if you right-click in a band and make it invisible, upon return of its' visibility, any controls within it are gone. I have tried this with various bands, and at least with my bits, this happens.
As well, the ordering of the bands is not yet consistent: the report header should always appears above the page header etc..
Cheers, drew..
As well, the ordering of the bands is not yet consistent: the report header should always appears above the page header etc..
Cheers, drew..
3 Answers, 1 is accepted
0
Hello drew,
I'm confused how exactly you make a section "invisible". While in design mode you can collapse a section to make room for the other sections and have better view of the rest of the report content. This can be achieved by clicking the section header's + sign. Expanding/collapsing a section is a design-time feature and it does not affect the report definition. The other way you can make a section (an item) invisible is by setting it Visible property to false. This property takes effect only at runtime while rendering the report. In design time all items are always visible regardless the value of the Telerik.Reporting.ReportItemBase.Visible property. Could you give us the steps you take so that we can reproduce the problem?
Thank you for the thoughts on the the sequence of the sections in the report designer. The current setup is by design and we have decided to do it this way after quite of discussion. Let me explain:
Page header and page footer always appear as topmost and respectively bottommost sections of the page. The place between them is where the report content goes. The Report Header section is part of the report content even if it appears only once at the top of the report. It makes sense to have the page header and footer on the first/last page. This is why we decided to show the page header and footer in design time this way. If this seems inconvenient, we are ready to rethink our position.
All the best,
Svetoslav
the telerik team
I'm confused how exactly you make a section "invisible". While in design mode you can collapse a section to make room for the other sections and have better view of the rest of the report content. This can be achieved by clicking the section header's + sign. Expanding/collapsing a section is a design-time feature and it does not affect the report definition. The other way you can make a section (an item) invisible is by setting it Visible property to false. This property takes effect only at runtime while rendering the report. In design time all items are always visible regardless the value of the Telerik.Reporting.ReportItemBase.Visible property. Could you give us the steps you take so that we can reproduce the problem?
Thank you for the thoughts on the the sequence of the sections in the report designer. The current setup is by design and we have decided to do it this way after quite of discussion. Let me explain:
Page header and page footer always appear as topmost and respectively bottommost sections of the page. The place between them is where the report content goes. The Report Header section is part of the report content even if it appears only once at the top of the report. It makes sense to have the page header and footer on the first/last page. This is why we decided to show the page header and footer in design time this way. If this seems inconvenient, we are ready to rethink our position.
All the best,
Svetoslav
the telerik team
0
drew
Top achievements
Rank 1
Rank 1
answered on 31 Jan 2007, 05:32 PM
howdy, bad choice of words on my part: simply right-clicking on a band, and unchecking the band, rendering it temporarily "invisible" in design-time. Ü
re the ordering: while it seems illogical to me, if it by design, i can get used to it , thanks kindly.. drew..
re the ordering: while it seems illogical to me, if it by design, i can get used to it , thanks kindly.. drew..
0
Hi drew,
I now understand what you're talking about. From the report's context menu you can add or remove the page header/footer and report header/footer sections, not just show/hide them. When you check any of these 4 sections, a new instance is being created and added to report's item collection. Then, when you uncheck it -- the section is being deleted from the design surface and removed from the report's item collection. The idea is that you can have only 1 instance of these 4 types of sections (in contrast to the groups and group header/footer sections).
For the official release we can consider a better UI to prevent further confusion and improve the usability of the report designer.
Regards,
Svetoslav
the telerik team
I now understand what you're talking about. From the report's context menu you can add or remove the page header/footer and report header/footer sections, not just show/hide them. When you check any of these 4 sections, a new instance is being created and added to report's item collection. Then, when you uncheck it -- the section is being deleted from the design surface and removed from the report's item collection. The idea is that you can have only 1 instance of these 4 types of sections (in contrast to the groups and group header/footer sections).
For the official release we can consider a better UI to prevent further confusion and improve the usability of the report designer.
Regards,
Svetoslav
the telerik team