Shulou(Shulou.com)06/01 Report--

How to create custom DevExpress report control, for this problem, this article details the corresponding analysis and solution, hoping to help more small partners who want to solve this problem find a simpler and easier way.

To help demystify report control development, here's how to create design-time settings, serialize designer components and related "bricks," and render and print components. The first part contains general information about the Swiss QR Bill control and describes the requirements of the control itself; the second part details the component implementation.

"Brick" implementation

general concept

VisualBrick is the basic element used to display data. VisualBrick elements consist of a data model (the brick) and its representation (the exporter).

Exporter renders and exports to a different format, specifying "brick" using the BrickExporter (Type) attribute of the "brick" setting. In this article, we use the descendants of PanelBrickExporter and VisualBrickExporter as exporters. The Draw method is rewritten to render, and the Brick field is used to gain access to the "brick."

To create a "brick," override the CreateBrick(VisualBrick[] childrenBricks) method and return an instance of "brick." The PutStateToBrick(VisualBrick, PrintingSystemBase ps) method maps control properties to "brick" data, see the code in the following file for more information: XRSwissQRBill.cs.

Selection of basic classes

The Swiss QR Control layout is an area with a text element and barcode in the middle, and the main choices for the basic classes are panels, tables, and the text "brick." The panel "brick" can place components inside with its simple results, so SwissQRBillBrick is based on the PanelBrick class and exporter is based on the PanelBrickExporter class.

Implementation of Service Brick

The specification states that the payment section may contain blank areas marked with corners. To meet this requirement, we created an extra CornerRectangleBrick and its exporter - CornerRectangleBrickExporter -which is responsible for drawing corners, and "brick" includes the BrickType attribute-which can be overridden for proper deserialization.

layout implementation

Select PanelBrick as the base class, and you can use the Bricks property to access its internal "bricks," coordinates relative to the panel itself-setting the internal "brick" coordinates relative to the point (0, 0).

Divide the component into receiving and paying section areas.

Rendering returns additional "bricks"(or combinations of "bricks"), which are then added to the Bricks collection.

CreateReceiptPart()

CreatePaymentPart()

Now we have to render the subregions.

CreateReceiptTitle()

CreateReceiptInformation()

CreateReceiptAmount()

CreateReceiptAcceptancePoint()

CreatePaymentTitle()

CreatePaymentSwissQRCode()

CreatePaymentAmount()

CreatePaymentInformation()

CreatePaymentFurtherInformation()

Please check the code in the following file for more information: SwissQRBillBrick.cs.

Exporter implementation

The exporter draws decorations on the finished "brick," which makes it possible to change the appearance in a preview or exported PDF file. In this article the exporter draws perforated lines and other text, the SeparatorKind option of brick determines what to draw, and the same mechanism for drawing "brick" is used for previewing and during PDF export, the main difference being that the IGraphics passed to the exporter's Draw method are objects with IPdfGraphics interfaces.

serialization

general concept

Both the control and the "brick" require serialization, the "brick" uses xml serialization only, and the control implements xml serialization and supports CodeDom serialization-a requirement for Visual Studio Designer.

Control serialization

The XtraSerializableProperty attribute is responsible for serializing attributes in xml, specifying attributes only to serialize attributes that return simple types, complex types require constructors with XtraSerializationVisibility parameter types (the most common values are Hidden, Collection, Reference, Content).

The DesignerSerializationVisibility property is responsible for CodeDOM serialization in Visual Studio Designer, it has only three variants of the related enumeration-hidden, visible, and content, marks a collection or reference with a visible attribute value, and the DefaultValue property determines whether the attribute value is included in the serialization.

Brick serialization

Only XML serialization is required, and in order to deserialize correctly, map the "brick's" text type (BrickType attribute overridden at the Brick level) to a true type. BrickFactory. The BrickResolve method is used for mapping. To implement the BrickResolve method, see the code in the following file: CustomControl.cs

component uses

To use a component in Visual Studio Designer, add it to Visual Studio Toolbox.

About how to create custom DevExpress report control questions to share the answer here, I hope the above content can be of some help to everyone, if you still have a lot of doubts not solved, you can pay attention to the industry information channel to learn more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.