These two functions are required by the IPrintableClient interface. The cells area ( GetGridBitmap) is delivered separately from the columns header area ( GetColumnsHeaderBitmap). The output, as you probably figured it out, is a bitmap. So, it has a third input parameter, a rectangle, which represents the desired part from the big picture. But in most of the cases, this would be too big to fit on a page. Having as input a data source and a table style, this class is able to make a virtual image of the data very similar with a layout of a DataGrid. Since printing the body of the report was too complicated to be done with print commands, a special class was totally dedicated to this task: PaintEngine. For the body, the bitmap is provided by a PaintEngine. For this, every block must be able to say its height and provide a bitmap with the correct size.įor the headers and footers, the technique is the same, and they are all of PrintElement type. After that, the PrintEngine iterates through the page collection of the PaginationEngine requiring from all constituent blocks of each page (headers, footers, and the body) to give a bitmap with their graphical representation (picture) and then simply paints them on the page, one under the other. Once initialized, the PaginationEngine creates a collection of pages with complete details of how every page should be constructed. That is why PrintEngine needs a PaginationEngine to provide the layout for every page in the report. PrintEngineĪ report can have more pages and their architecture might not be the same (only the first page has a Report Header and only the last one has a Report Footer, etc.). The layout for the Body (which is very similar with the DataGrid's layout) is provided by a PaintEngine. It is both simple and effective, but is not a good solution for representing complicated structures which can expand on more than one page in both directions. A PrintCommand is very suitable for printing text, lines, and other simple things, and it has always the width of the page, and a limited height (in this case, 200 pixels). The footers and headers are collections of print commands (Text, Picture, Date, etc.). A page has five constituent parts (or blocks): the Report Header, the Page Header, the Body, the Page Footer, and the Report Footer.
Technically, the report is a collection of pages. They communicate to each other through two interfaces: IPrintableClient and IPaginationClient. PrintEngine inherits from PrintDocument and executes tasks related with the printing process, while PaintEngine is dedicated to the task of drawing the data from the DataSource on bitmaps. ReportBuilder is a wrapper class that contains and exposes the main fields of two specialized classes: PrintEngine and PaintEngine. In order to understand how this component works, you should be familiar with the printing process in. When you open the solution for the first time, you should compile it before doing anything else. Use it on your own risk, and please send a feedback with the found bugs.
Notice that for the first column, you can't change neither the Width nor the BackColor. Click on the button labeled "Print Grid" to see a custom report of the DataGrid on the form. These reports are designed by the programmer at design-time. If it changes to Cursors.Hand (I was too lazy to make a more suggestive cursor) it means that the control has an automatic print support. Moving the mouse over different controls you will notice that the mouse cursor changes. To check this, click on the toolbar button labeled "Print Assistant".
Its architecture is based on DataView, and it receives as data source anything from which it can extract one: DataTable, DataView, DataGrid, ComboBox, ListBox and IReportSource. ReportBuilder doesn't target a specific control, like DataGrid or ComboBox, instead it's focusing on the data source that these controls use. The goal of this component is to provide an easy, direct, and customizable solution for printing the data that you normally process in a database driven application. NET is easier than ever before, it's still not accessible to everyone. This is a simple report builder component with the possibility of designing the report both at design and run-time and with a wide variety of candidates for the data source.
0 kommentar(er)
