Hi,
Since we want to boost up the performance of the ScheduleView , we've applied the 2023_2_718 UI for WPF to enable the virtualization of the group headers with setting the property IsGroupHeadersVirtualizationEnabled="True". However we've experienced issues also with rendering for the appointments and group headers(resources) when scrolling.
In one of the screens where the schedule view is used, the group headers don't have equal sizes, for example:
The height may vary depending on the overlapping appointments for the resource which is allowed for our system.
There is a note that there might be issues and unexpected behavior when the headers have different sizes claimed here:
WPF ScheduleView - UI Virtualization - Telerik UI for WPF
In this scenario we experience multiple issues, like for example when scrolled at the bottom, and the schedule view is fully refreshed, the resources and appointments are not rendered :
until it's scrolled.
Also when scrolling, we experience a "blinking" rendering, the group headers change sizes on scrolling :
Can you please let us know if/when this is planned to be fixed.
Another issue not related to the header size differences is that some of the appointments are lost (not rendered) when the height of the schedule view is changed resulting in some of the appointments to not be visible anymore .The selection is kept on the group headers, but the appointments are not rendered.
Thank you!
When the focus gets in RadRichTextBox, AutomationProperties.Name is not pronounced by screen readers (for example by Windows Narrator).
I just completed an evaluation of the RadPdfProcessing library for our medical practices. Unfortunately, we are not yet able to use this library for our application. We need to be able to annotate patient visit reports when visit notes require amendments or when we appeal billing decisions. We do this frequently and we need a way to automate this tedious and time consuming process. While the vision for the RadPdfViewer (ref. Unifying the Power of PdfViewer & PdfProcessing: Edit a PDF with our Newest Secret (6/12/2020)) was promising, there are still some issues for us. Following is a list of areas where we would like to see improvements:
1. We need the ability to add notes (like when editing is enabled in the AddDocumentContent_WPF sample application). But also be able to control font, font size, bolding, underlining, and highlighting and text color. Also we need to be able to go back and edit text and text formatting after new text is added and the text editing window closes. This is not yet possible. Ideally, this text also needs to allow multiple text fragments (Run's) where each text fragment can have its own formatting (bolding, color, etc.).
2. Each note needs to be in an optional bubble or box with an optional line or arrow to the highlighted (or strike-through) text in the original document. It would also be helpful if the bubble could be reshaped and moved to a more optimum location while maintaining the connecting line to the associated highlighted text. Automatically positioning the bubble when it is first created in adjacent white space is also desired.
4. We would like the above functionality to be implemented via a right click context menu for selected text in the original document. A command like "strike-through text and open note would be ideal".
5. If possible we also would like to pre-edit a pdf file as a RadFixedDocument and perform some or all of the above operations before the document is displayed in the RadPdfViewer. To do this we will need to be able to search for text in a given location in the pdf, select that text and then perform the desired operations (described above in 3. and 4.). This is needed for a majority of the changes that we need to make, that is, in sections of the document that we know from experience always require the same annotations. We see this functionality being integrated with AI enabled processes that are able to find and prepare billing appeals and assist with patient record amendments.
Respectfully, Bill Goforth, Professional Imaging LLC, Medical Systems Development, 360-528-1844
Hello,
I want to report a bug with text color in textbox and presumably in some other controls. When the textbox is edited, then the color is correctly black:
Telerik: 
But when the textbox loses focus, it changes the color to gray, which is hard to read and looks like disabled:
Telerik: 
Thanks
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
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
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
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)