What you have two separate RadDocking controls it should be possible to drag a Pane from the first control into the other one.

Hello together,

I am experiencing a bug with the following use case:

1. Import an existing PDF file
2. Modify the PDF file
3. Export the PDF file

When upgrading Telerik.Documents.Fixed from version 2024.3.806 to version 2024.4.1106 the exported PDF file is missing different parts of the originally imported PDF file or even results in a complete "messy" file. Input and output files are view with Adobe Acrobat, Google Chrome, Edge...all showing the same result.

Even omitting step 2 (i.e. I only import and directly export the PDF file) results in the same bug after.

I do not use any special import or export setting to reproduce the error. But even with applying different import/export settings I could not change the buggy outcome.

var bytes = File.ReadAllBytes(@"C:\temp\in.pdf");
var formatProvider = new PdfFormatProvider();
var document = formatProvider.Import(bytes, TimeSpan.FromSeconds(20));
var outBytes = formatProvider.Export(document, TimeSpan.FromSeconds(20));
File.WriteAllBytes(@"C:\temp\out.pdf", outBytes);

See the attached file for example, import it and export it (via code snippet above).

With version 2024.3.806 everything works fine - and as I am not seeing any relevant breaking changes or other release information regarding this issue, I am a little bit lost with what I could do to solve the issue..

Thanks for your support!

Improve the load time when the ribbon UI is used.

Hello,

HtmlDataProvider will throw an exception on export or when used by a RadRichTextBox, when using a html containing the length value "NaN", which doesn't seem to be a standard approved value, but nevetheless it is a special case because other invaild values are simply ignored while this one triggers two exceptions - one of which is hard to catch and crashes the whole application.

Code to reproduce:  Console App / .Net Framework 4.8 / Package Telerik.Windows.Documents.FormatProviders.Html.for.Wpf 2022.3.912

using System;
using Telerik.Windows.Documents.FormatProviders.Html;
using Telerik.Windows.Documents.Model;

namespaceHtmlProviderCrash
{
    internalclassProgram
    {
        static void Main(string[] args)
        {
            var htmlContent = "<img src=\"https://static.cleverpush.com/notification/icon/92fYF7FtKbthsezwS.png?element=Le7adDwC\" " +
"alt=\"\" style=\"display: inline-table;max-width: 100%;width: 300px;\" width=\"300\" height=\"NaN\" class=\"cp-element-image light-img\">";

            HtmlFormatProvider htmlProvider = new HtmlFormatProvider();
            RadDocument document = htmlProvider.Import(htmlContent);

            try
            {
                var export = htmlProvider.Export(document);
            }
            catch (Exception ex)
            {
                var ka = ex.ToString();
            }
            while (Console.ReadKey().KeyChar != 'x') { }
        }
    }
}
   

Message	"MeasureOverride returned NaN: Telerik.Windows.Documents.Layout.ImageLayoutBox"	string

at Telerik.Windows.Documents.Layout.LayoutElement.Measure(SizeF availableSize)
   at Telerik.Windows.Documents.Layout.ParagraphLayoutBox.MeasureCurrentGroupSize(ParagraphLayoutBoxMeasureContext context, SizeF measureSize, Func`1 GetCurrentXDefaultValue, LinkedList`1 currentGroupInlines)
   at Telerik.Windows.Documents.Layout.ParagraphLayoutBox.MeasureOverride(SizeF availableSize)
   at Telerik.Windows.Documents.Layout.LayoutElement.MeasureCore(SizeF availableSize)
   at Telerik.Windows.Documents.Layout.LayoutElement.Measure(SizeF availableSize)
   at Telerik.Windows.Documents.Layout.SectionLayoutBox.MeasureOverrideInternal(SizeF availableSize)
   at Telerik.Windows.Documents.Layout.SectionLayoutBox.MeasureOverride(SizeF availableSize)
   at Telerik.Windows.Documents.Layout.LayoutElement.MeasureCore(SizeF availableSize)
   at Telerik.Windows.Documents.Layout.LayoutElement.Measure(SizeF availableSize)
   at Telerik.Windows.Documents.Layout.DocumentLayoutBox.MeasureOverrideInternal(SizeF availableSize)
   at Telerik.Windows.Documents.Layout.DocumentLayoutBox.MeasureOverride(SizeF availableSize)
   at Telerik.Windows.Documents.Layout.LayoutElement.MeasureCore(SizeF availableSize)
   at Telerik.Windows.Documents.Layout.LayoutElement.Measure(SizeF availableSize)
   at Telerik.Windows.Documents.Model.RadDocument.Measure(SizeF measureSize)
   at Telerik.Windows.Documents.Model.RadDocument.MeasureAndArrangeInDefaultSize()
   at Telerik.Windows.Documents.Model.RadDocument.EnsureDocumentMeasuredAndArranged()
   at Telerik.Windows.Documents.FormatProviders.Html.Export.HtmlDocumentExporter.Export(RadDocument document, Stream output)
   at Telerik.Windows.Documents.FormatProviders.Html.HtmlFormatProvider.Export(RadDocument document, Stream output)
   at Telerik.Windows.Documents.FormatProviders.Html.HtmlFormatProvider.Export(RadDocument document)
   at HtmlProviderCrash.Program.Main(String[] args)

Message	"The image data generated an overflow during processing"
   at System.Windows.Media.Imaging.TransformedBitmap.FinalizeCreation() in System.Windows.Media.Imaging\TransformedBitmap.cs:line 216
   at System.Windows.Media.Imaging.TransformedBitmap.EndInit() in System.Windows.Media.Imaging\TransformedBitmap.cs:line 112
   at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation() in System.Windows.Media.Imaging\BitmapImage.cs:line 505
   at System.Windows.Media.Imaging.BitmapImage.EndInit() in System.Windows.Media.Imaging\BitmapImage.cs:line 319
   at Telerik.Windows.Documents.Model.ImageDocumentElementHelper.CreateImageSourceCore(BitmapCreateOptions createOptions, Byte[] bytes, Size renderingSize, String& extension, Byte[]& resultBytes)
   at Telerik.Windows.Documents.Model.ImageDocumentElementHelper.CreateImageSource(Byte[] bytes, Size imageSize, Size scaleFactor, String& extension, Byte[]& resultBytes)
   at Telerik.Windows.Documents.Model.ImageDocumentElementHelper.InitializeRawImageData(IImageDocumentElement imageElement, Byte[] bytes, Size scaleFactor, String& extension)
   at Telerik.Windows.Documents.Model.ImageDocumentElementHelper.InitInternal(IImageDocumentElement imageElement, Byte[] bytes, Size size, String extension, Boolean isUserInitiated)
   at Telerik.Windows.Documents.Model.ImageInline.InitImageElementFromUriStream(Stream stream)
   at Telerik.Windows.Documents.Model.ImageInline.<SetStreamFromUriSource>b__0(Object s, StreamReadyEventArgs a)
   at Telerik.Windows.Documents.Utils.ResourceStreamLocator.OnStreamReady()
   at Telerik.Windows.Documents.Utils.ResourceStreamLocator.<GetStreamAsync>b__0(Object sender, OpenReadCompletedEventArgs e)
   at System.Net.WebClient.OnOpenReadCompleted(OpenReadCompletedEventArgs e)
   at System.Net.WebClient.OpenReadOperationCompleted(Object arg)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Hi Telerik-Team,

the 2024.4.X release of UI for WPF seems to no longer render pdf files correctly. It looks like as if the PdfViewer just renders the document as a single huge page.

An application that uses those references:

<PackageReference Include="Telerik.Windows.Controls.for.Wpf.Xaml" Version="2024.3.924" />
<PackageReference Include="Telerik.Windows.Controls.FixedDocumentViewers.for.Wpf.Xaml" Version="2024.3.924" />
<PackageReference Include="Telerik.Windows.Documents.Core" Version="2024.3.806" />
<PackageReference Include="Telerik.Windows.Documents.Fixed" Version="2024.3.806" />
<PackageReference Include="Telerik.Windows.Zip" Version="2024.3.806" />

works as expected. Once you change those to:

<PackageReference Include="Telerik.Windows.Controls.for.Wpf.Xaml" Version="2024.4.1111" />
<PackageReference Include="Telerik.Windows.Controls.FixedDocumentViewers.for.Wpf.Xaml" Version="2024.4.1111" />
<PackageReference Include="Telerik.Windows.Documents.Core" Version="2024.4.106" />
<PackageReference Include="Telerik.Windows.Documents.Fixed" Version="2024.4.106" />
<PackageReference Include="Telerik.Windows.Zip" Version="2024.4.106" />

the renderer stops working.

I have attached a VS solution with a pdf file that reproduces this

In a multi monitor scenario with different scalings and an application that is configured to run ‚per monitor dpi awareness‘ a floating toolwindow cannot be docked at all positions.

Example:

Monitor 1: 1920 x 1200 (100%), Monitor 2: 2048 x 2560 (150%)

Our WPF application has a main window, maximized on screen 1 and a child window maximized on screen 2.

In the app.manifest we use per monitor dpi awareness.

Both windows have a RadDocking instance with a docked RadPane. Start the application, undock a tool window and try to dock it at the right position on monitor 1.

è It is not possible since the compass is deactivated before the mouse cursor reaches the right monitor area.

After upgrading to .net 9 I get the following error when starting the published program (running it in RIDER in debug-mode doesn't create the issue).

System.TypeInitializationException: The type initializer for 'Telerik.Windows.Input.Touch.TouchManager' threw an exception.
 ---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Windows.Forms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. Das System kann die angegebene Datei nicht finden.

the mentioned assembly System.Windows.Forms is not used by me at all.

Suddenly with WPF release 2024 Q4 some of pdf-s are not presented correctly. Attached file was produced with Telerik Report Designer and exported as pdf. With previous WPF version was OK.

You can check in your demo application. It is shown in previous release but not with latest.

Please make solution ASAP.

Regards
Janez Ovsenik

Hi, we have many documents (drawings) and these documents are full of stamps. Unfortunately the pdfviewer does not show them.

I am only asking for rendering stamps properly, not creating or modifying. I want to see the stamps. I also see that some stamps are rendered, not all, but some and they are displayed off the document. as if they were rotated 90deg. If no support is added, at least correct the position they are displayed at.

I have attached two pictures, one opened in Adobe and one with the viewer in my app.

Please consider at least fixing the display, even if no support for stamps is provided. Just display it correctly. By the way the stamps have not been flattened. that is intentional.

Thanks,

When the focus gets in RadRichTextBox, AutomationProperties.Name is not pronounced by screen readers (for example by Windows Narrator).

Here's an idea for you, one which I haven't fully thought through but which I will post here in case it proves useful.

For my use case we am required to build the Telerik UI for WPF binaries from the source code. This is because we offer our product as a trial version which requires the source files to be protected.

Building the source takes a bit of time whenever there is a new version and we have to remember to copy and replace the modified source protection files before we build the binaries.

My suggestion would be to move the file protection code into a single separate class library (DLL) and provide the source code that can be modified by the end user and rebuilt into the file protection DLL.

Then rather than having to rebuild the entire source code from scratch whenever there is a new version, we could just use the installer to install the new binaries and just replace the FileProtection.dll file.

That way when there is a new version of UI for WPF (or whatever product) we could quickly update to it and then when we build our product installer we just copy the modified FileProtection.dll to be bundled alongside the Telerik binaries.

As I said I haven't thought this through all the way and there may be excellent reasons why you are unable to do this, but I thought I'd share the idea.

HTH Richard