Currently PropertyDefinitions have only one Property for DataBinding, which is very strange solution.

All these instances are DependencyObject, but at the same time they are not in the visual tree and we could not bind to a visibility or to readonly or to any other property without some starnge sorkarounds (why this was designed in this way?).

This makes these objects almost useless. becuae we cannot fully use them in an MVVM way (bindings, multiibindings, etc.)

Possible solutions:

1. provide bindings for all properties to make them be bindable withput any workarounds
2. Change PropertyDefinitions to something that will live inside visual tree.

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,

- collision with classes CallbackBehaviour and ConcurrencyMode, collision with DuplexChannelFactory

- Collision with SecurityPolicyVersion and may others types in System.ServiceModel.Security Namespace | Microsoft Learn

- [Breaking change]: WCF Client 6.0 release will no longer support net standard 2.0 · Issue #33515 · dotnet/docs · GitHub

- - large amount of 40 unnecessary dependencies. These are potential errors in Nuget dependecy resolution.

9,4 MB unnecessary additional files per application.

-Only necessary dependencies should be added.

It is possible for a user to type a value into a RadNumericUpDown control that is greater than the maximum (or smaller than the minimum).

If the control loses focus the value reverts to the maximum value, but in my use case the user will be clicking the OK button on a Window, and this happens while the NumericUpDown still displays the out of range value that was typed. In other words the user doesn't realise that their value was silently rejected behind the scenes.

To solve this I had to raise a support request with you guys, which meant waiting until the next day for a resolution. This cost me time and it also added to your workload.

Whereas if the control had the option to limit the user input to the bounds of minimum and maximum it would have saved me about half a days work to raise a support request and write my own solution to the problem.

I see this has been raised a couple of times in the forums:

https://www.telerik.com/forums/prevent-user-from-typing-beyond-maximum-value

https://www.telerik.com/forums/radnumericupdown-lets-you-type-beyond-its-maximum-value

And the consensus seems to be that it is "By Design".

Please can you re-consider changing this as it is these small niggles that often cost us the most time when developing with 3rd party controls.

TIA

Use Case

our users have the possibility to save and load their own RadGridView filter settings.

One user want to get all entries where the value of the property \ column "CreateionDateUtc" is older than 90 days.

Problem

Currently you can only configure Is Less Than "Fixed Date". That means you have to change the "Fixed Date" every day to get the required result.

Is there a possibility to add a filter to the DateTime Column for example Less than 90 Days?

Possible Solution

Possibility to add a Time Difference Filter

- Base (Datetime.Now, Datetime.UtcNow,.....)

- Unit (second, minutes, day, month, years,....)

- Count

Wrong XAML files are shipped with the Net Core themes archive. Instead of Docuemnts.xaml and RichTextBoxUI.xaml the RichTextBox.xaml file should be added. 

We can add a new control similar to the ToolbarForm control from the Telerik UI for WinForms:

Overview - RadToolbarForm - Telerik UI for WinForms

Steps to reproduce: 

1. Download Telerik_UI_for_WPF_Source_[Version].zip

2. Modify the Release70 configuration to Debug70 in the following script - Build_WPF70_Xamlless.bat

3. Execute the bat file to reproduce the error:

Telerik_UI_for_WPF_Source_[Version]\Core\Controls\Input\Touch\TouchManagerV3\TouchManager.TouchMode.cs(242,9): error CS1519: Invalid token '{' in class, record, struct, or interface member declaration [D:\temp\tic\Telerik_UI_for_WPF_Source_2023_3_1114\Core\Controls\Controls_NetCore_5cmyf5ge_wpftmp.csproj::TargetFramework=net7.0-windows]

As I workaround I would suggest editing the NetCoreConfigurations.targets with the following property groups: 

<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug70|AnyCPU' ">
    <TargetFrameworks>net7.0-windows</TargetFrameworks>
    <PlatformTarget>AnyCPU</PlatformTarget>
    <DebugSymbols>true</DebugSymbols>
    <DebugType>full</DebugType>
    <OutputPath>bin\$(Configuration)\</OutputPath>
    <DefineConstants>DEBUG;WPF;NETCORE;CODE_ANALYSIS;WPF45;WPF40</DefineConstants>
    <TreatWarningsAsErrors>false</TreatWarningsAsErrors>
    <WarningsAsErrors />
    <SourceAnalysisTreatErrorsAsWarnings>true</SourceAnalysisTreatErrorsAsWarnings>
    <StyleCopEnabled>false</StyleCopEnabled>
    <TargetFrameworkVersionString>70</TargetFrameworkVersionString>
  </PropertyGroup>

  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug70.NoXaml|AnyCPU' ">
    <TargetFrameworks>net7.0-windows</TargetFrameworks>
    <PlatformTarget>AnyCPU</PlatformTarget>
    <DebugSymbols>true</DebugSymbols>
    <DebugType>full</DebugType>
    <OutputPath>bin\$(Configuration)\</OutputPath>
    <DefineConstants>DEBUG;WPF;NETCORE;CODE_ANALYSIS;WPF45;WPF40;NOXAML</DefineConstants>
    <TreatWarningsAsErrors>false</TreatWarningsAsErrors>
    <WarningsAsErrors />
    <SourceAnalysisTreatErrorsAsWarnings>true</SourceAnalysisTreatErrorsAsWarnings>
    <StyleCopEnabled>false</StyleCopEnabled>
    <NoXaml>true</NoXaml>
    <GenerateImplicitStyles>true</GenerateImplicitStyles>
    <TargetFrameworkVersionString>70</TargetFrameworkVersionString>
  </PropertyGroup> 

The file can be found here: Telerik_UI_for_WPF_Source_[Version]\Build\Imports\NetCoreConfigurations.targets.

Using RadTabbedWindow I noticed difficulty dragging maximized windows between monitors. It seems to happen in multi-monitor environments and only when dragging Left of the PrimaryScreen.

In the video I've included , the blue window is a standard window and can be maximized in one drag across any display.

The white window is RadTabbedWindow and the drag will default to the PrimaryScreen when dragged to the left-most display.

Any help would be appreciated. Thanks