CircularArrowShape has wrong geometry

Hi,

I download the source code 'Telerik_UI_for_WPF_Source_2022_1_117' and then I want to run 'Build_WPF60.bat' [\Telerik_UI_for_WPF_Source_2022_1_117\Build\BatFiles]. An error occurs, see the attachment: 'Could not locate the assembly "Telerik.Windows.Documents.Core".' I tried it on Win 10 and Win 11 with installed VS202

2."

Best regards
Huráb Radek

Make sure all properties are rising OnPropertyChanged event.

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

Telerik assemblies needs to be rebuild with a specific key in some redistribution scenarios, so that the assemblies can be bound only to a single WPF application. This is described in the following article: https://docs.telerik.com/devtools/wpf/licensing/protecting-telerik-assembly

Currently, to protect the dlls you need to rebuild the entire source code of Telerik UI for WPF. Sometimes this is not very convenient and it is prompt to errors because several steps should be followed and also few prerequisites should be met.

Consider providing a new mechanism to protect the Telerik assemblies, which is more convenient and gives better protection. 

In our app many checkboxes are crop when user scale to 125 %, it happens in win11 but it has been reported in win10.

I found out that this is also happening in the colour theme generator from Telerik with the checkbox in the ribbon (screenshot below).

Is this a known issue or something that we can fix some how? so far we have taken the template for the checkboxes and change the margin of the element "grid" from 1 to 0 to work around it. 

Thanks in advance

Julio

Its been two years since you were last asked for this, and you said when it gets traction. 

Well, its getting traction, v11 is coming out, there is ever increasing list of public projects, https://avaloniaui.net/Showcase, plus countless WPF inhouse migrations like the ones we do. Serious money is already being involved, there are already many teams who would rather pay you for controls than waste their own cycles repeatedly making functionality. 
WPF is indeed dying, .net foundation is treating it like a leprous uncle, Avalonia is literally getting more love from some foundation projects than WPF does, some wpf libraries are still targeting net5 with no intention to update them. MS wants you to migrate away from it to MAUI (after failing to get us to migrate to UWP) and it lacks cross platform support which neither of MS replacements like MAUI offer, and MS has a big influence over what they do. Chances of that succeeding are very slim, as big as they were for UWP. Even barring the lack of Linux support, WPF has this pre-mortem smell that Silverlight had, people stick to WPF becuase there really is no roadmap that will retain full functionality.

Chicken and the egg debate is losing its appeal, we are presently even willing to sacrifice some functionality to get away from WPF before it sinks. 

The writing is on the wall, there is a clear and present need for quality commercial 3rd party controls for Avalonia, from the paying customers. I understand there is work to port the styling in WPF controls and to remove any windows P/I dependencies you might have. But whoever of you largest control makers steps on the market first and opens the flood gates, will get the first revenue and a foot in the porting of larger WPF projects, and certainly the inertia going forward.  I am posting this to each of you. 



Time to wake up. "Wake up and smell the ashes" :)

If the total Items count exceed the MaxVisiblePips value,scroll by mousewheel,when scroll to the start or end item,the next scroll item should be the end or start,

the scrollview can not scroll to the selected item. Please see Annexes 1 and 2

When  the MaxVisiblePips value is four,click the right item ,The scroll view cannot be rolled to the center, Please see Annexes 3

We are looking for a feature to group Tabs in the TabbedWindow similar to the way modern browser handle this.

Hold down the Ctrl key and click each tab to select multiple tabs

Trigger method "AddTabsToGroup"

Have different Styling (colors) for each Group. be able to name groups in code and display group name

Remove Groups in Code

 

 

Since we are working with large TreeViews users some times get confused about the current parent of an Element.

It would be useful if the parents of on element would sticky to the top of the control. 

Similar to functionatlity of the Sticky Group Headers for the RadGridView or the newly introduced Sticky scroll in Visual Studio

https://docs.telerik.com/devtools/wpf/controls/radgridview/grouping/stickygroupheaders

 

Currently, the same glyph is used both when the RadRibbonWindow is maximized and in a normal state.

Develop  a new control - Fisheye Panel.

New control request: FishEye menu.

A new Tag Cloud control similar to the WinForms and ASP.NET Ajax counterparts (http://demos.telerik.com/aspnet-ajax/tagcloud/examples/overview/defaultcs.aspx)

Introduce a new theme with the Windows 11 look but with smaller sizes.

Create a SlideView control like the one in the Telerik UWP suite.
https://docs.telerik.com/devtools/xamarin/controls/slideview/slideview-getting-started

The control should  have a content area, previous and next buttons, and dots indicator below, that indicates the currently selected page.

If a formula contains a named range as an argument, its value may not get updated properly in the following scenario:

In the formula: =SUMIF(A1:A4, 3, ColumnC), ColumnC is a named range refering to C1:C4. Range A1:A4 contains the values 3, 2, 2, 3, which will avoid a circular reference. The formula is entered twice, in C2 and C3. Note that these cells are part of the range ColumnC refers to. When you refresh the formula in C3 (enter edit mode, then press enter), it will calculate correctly, but the formula in C2 will be recalculated to an error. If you refresh the formula in C2, the formula in C3 will be evaluated to an error.