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.
A XamlParseException is raised when the theme's resource dictionaries are not merged in App.xaml. The missing resource is the RepeatButtonStyle resource.
To work this around, merge the resource dictionaries for the theme in the Resources collection of the App.xaml file.
When trying to install one of the following nuget packages an error occurs:
- Telerik.Windows.Controls.EntityFramework60.for.Wpf.Xaml
- Telerik.UI.for.Wpf.AllControls.Xaml (which contains the EF6 package from the previous bullet)
The same issue manifests with the NoXaml version of the same packages.
The error message is:
Severity Code Description Project File Line Suppression State Details Error Failed to add reference. The package 'Telerik.Windows.Controls.EntityFramework60.for.Wpf.Xaml' tried to add a framework reference to 'EntityFramework' which was not found in the GAC. This is possibly a bug in the package. Please contact the package owners for assistance. Reference unavailable.
Currently the Windows 11 theme for Telerik WPF features the ability to switch backdrop material to Acrylic, Mica and None, but what it's missing the Mica ALT material.
Because of the substantial difference from the normal Mica material, and the ability it gives to create more modern looking applications we think that the addition of this backdrop material would greatly benefit an already very good looking theme!
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:
- provide bindings for all properties to make them be bindable withput any workarounds
- 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,
The visual indicator of the selected area is slightly above the text as you can see in the attached screenshot.
You can find a fully reproducable example in the attachments
- collision with classes CallbackBehaviour and ConcurrencyMode, collision with DuplexChannelFactory
- Collision with SecurityPolicyVersion and may others types in System.ServiceModel.Security Namespace | Microsoft Learn
- - 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
When null value is provided the converter should return Visibility.Collapsed.