Hi Telerik Team,

I am using telerik reporting watermark to put some "design" in our report template for all the pages, but a small image with a size of 50kb as watermark generates additional 200-300MB of memory usage during the rendering of the report.

Please reduce the memory consumption since this behavior limits the number of user that can access the report simultaneously

Thanks 

Ways to reproduce the problem:

1. Create simple one table one column report, with right horizontal text alignment in the column.

2. Set a data source with multiple rows, with different lengths for the string, displayed in the table's column.

3. Render the report under Windows and under Linux - the column text on different rows will not be aligned properly on linux, but will be shifted to the left or right depending on string's contents and length.

I've done a bit reserch on PDF rendering, concerning libgdiplus "MeasureString" method deficiencies, and here's what I discovered so far:

1. The source of the problem is the fact that libgdiplus ends up using cairo to measure string glyphs, and it does it's font metric in whole pixels (integer), using the DPI of the context it is called in. In short, if the context is using 96DPI, cairo will use these 96DPI to calculate (and round) the font metrics, and to write strings eventually.

2. When libgdiplus is compiled to use pango, the problem is much smaller (several millimeter differences become part of the millimeter), because internally pango scales the measurement 1024 times, but it appears that this is not enough to resolve the problem.

3. When using libgdiplus (with or without pango inbetween it and cairo) for both "DrawString" and "MeasureString", everything is perfect, but the fundamental problem in Relerik Reporting to PDF is that it renders in a vector format, but uses text metering for pixel format - it uses System.Graphics.MeasureString which is a DPI vased metering (on Linux at least) but uses proprietary "PdfRenderer.DrawString" of the "PdfRendered" class, not the native Graphics.DrawString. Since cairo rounds every character glyph metrics to an integer value, the longer the string is, the larger the discrepancy will be between string rendering when PDF is viewed (based on floats/doubles) and Graphics.MeasureString (based on integers, at least on Linux).

Ways to resolve the issue:

1. The best way to resolve the issue is not to call Graphics.MeasureString at all, when rendering to vector based format, because it measures string based on the DPI on graphics context it is in. In other words, proprietary "PdfRenderer.MeasureString" must be  implemented, which works with font glyphs directly, entirely using single or double precision math to calculate glyph dimensions and string dimensions.

2. Another, not so perfect, but HUGELY EASIER way is to set DPI of the rendering context of the PDF to a higher value, here's how:

public PdfContext(string ownerPassword, string userPassword)
{
            this.dataFormatter = string.IsNullOrWhiteSpace(ownerPassword) ?
                                    new DataFormatter() :
                                    new DataFormatterEncypted(ownerPassword, userPassword);

            this.bmp = new Bitmap(1, 1);
            this.graphics = Graphics.FromImage(this.bmp);
            this.hdc = this.graphics.GetHdc();
            this.pdfFontCache = new PdfFontCache();
 }

public PdfContext(string ownerPassword, string userPassword)
{
    this.dataFormatter = string.IsNullOrWhiteSpace(ownerPassword) ?
                            new DataFormatter() :
                            new DataFormatterEncypted(ownerPassword, userPassword);

    this.bmp = new Bitmap(1, 1);
    bmp.SetResolution(9600, 9600); //ADDED
    this.graphics = Graphics.FromImage(this.bmp);
    this.hdc = this.graphics.GetHdc();
    this.pdfFontCache = new PdfFontCache();
}

I need to set a structured heading tags like <h2><h3> (https://www.w3.org/TR/WCAG20-TECHS/PDF9.html) so the pdf file can have those tags.

Please make the Reporting support more various tags so pdf files can have structured tags.

Hello, 

I am using the Blazor Web Report Designer on a page that is not the default route, i.e. "/". When I am at step 2 in the WebServiceDataSource wizard to add parameters, if I click the Add Parameter button it routes to the home page. 

I believe this is caused by the href="#' empty route. Below is an animation of what I mean. This is also reproduced in the BlazorIntegrationDemo in the installation directory.

Error: Unable to cast object of type 'Telerik.Reporting.Processing.Expressions.ProcessingEvalProvider' to type 'Telerik.Reporting.Expression.IValueObject'

is thrown on previewing the data source results in the WebServiceDataSource when the Runtime or Design time expressions are left completely empty or the runtime value is a report parameter with an empty Value property.

The following error is thrown when inserting a new column on merged columns in a crosstab/table and then trying to select that column:

"Value cannot be null. Parameter name: components"

I like the new open dialog for the Web Report Designer, but now my report names are all truncated and I can't tell what anything is.  Can you please off a list view in the Open Dialog so all my names aren't "Company R..."

Currently, the Web Report Designer does not allow one to insert a report item in place of a table cell textbox.

Meanwhile, the Standalone Designer does allow such operations.

Hi,

Does the Web Report Designer support zooming of the report area? Similar to the Standalone designer:

Best regards,

Magnus

Please add DropDownTree and/or TreeView as single- and multi-value parameter editors to accommodate Hierarchical data. It would be nice to have them out-of-the-box when available values come from a hierarchical/self-referencing table(s), but I would be happy if they could be integrated as Custom Parameter Editors. I was able to render and populate the dropdowntree with checkboxes, pass the correct selected values, but the 'Preview' button would never enable upon selection. Also, the dropdowntree's AutoClose(false) was not recognized. I know this can be achieved outside of the report viewer, but sometimes that method disrupts the layout and flow of the reporting view.