Your feedback is greatly appreciated. However, as my colleague, Hristo, had previously explained we have no control on how native GDI is working internally and how the characters are painted. Changing the whole text rendering mechanism in RadRichTextEditor is a very massive task and it may affect existing customers' applications. It should be planned very precisely and consider all possible options for improving the text before addressing it. Feel free to track its progress and subscribe for status changes.
Posted on:04 Jan 2018 08:30
I completely agree with Thomas' comment. This must be fixed.
Posted on:28 Nov 2017 13:05
Fair enough but all the other controls still have the same issues.
The rendering just looks completely different than any other native windows program.
The user feedback on this was massively negative so we were forced to switch to UseCompatibleTextRendering = false for now.
But this creates a whole lot of bugs (some of which are 5 years old and still not fixed), and degrades the performance.
The negative feedback is completly understandably because the text is just unreadable in some conditions, very straining to read (blurry) and has very inconistent kerning.
We cannot justify this blurry, ugly text to our users just for some "technical" problems that only our program seem to have.
You advertise your controls with "Unrivaled Performance and User Experience" but this is the complete opposite.
The font rendering needs to be fixed for all controls.
Posted on:19 Jul 2017 10:57
GDI and GDI+ can be switched and each has its pros and cons. For our controls we have decided that by default we will use GDI+. We have no control on how these Windows API are working internally and how the characters are painted. Some detailed information and comparisons are available here: https://theartofdev.com/2014/04/21/text-rendering-methods-comparison-or-gdi-vs-gdi-revised/. The Graphics class in GDI+ is significantly faster than the TextRenderer used by GDI.
The described issue in RadRichTextEditor is actually not at all related to the GDI+. RadRichTextEditor is a complex control and we have decided to use native GDI rendering for the text(not GDI or GDI+). For the purpose we are using the gdi32.dll and its TextOut function: https://msdn.microsoft.com/en-us/library/dd145133(v=vs.85).aspx.
Posted on:31 May 2017 07:42
Is bug is present in ALL controls when using GDI+ (UseCompatibleTextRendering = true).
This is a general rendering bug in the text rendering of telerik winforms and should be fixed for all controls not only the RadRichTextBox
Posted on:15 Apr 2016 09:49
The irregular character spacing makes it look like long words are split into smaller words. This affects readability.