When RTF documents are imported simultaneously in different threads, sometimes ArgumentException with message "An item with the same key has already been added" is thrown with the following call stack: at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value) at Telerik.Windows.Documents.FormatProviders.ReplaceStyleNameHandler.Add(String displayName, String name) at Telerik.Windows.Documents.FormatProviders.ReplaceStyleNameHandler.InitializeStyleDisplayNameToStyleNameDictionary() at Telerik.Windows.Documents.FormatProviders.ReplaceStyleNameHandler.get_StyleDisplayNameToStyleName() at Telerik.Windows.Documents.FormatProviders.ReplaceStyleNameHandler.TryGetStyleNamesByStyleName(String displayName, RadDocumentDefaultStyleInfo& defaultStyleInfo) at Telerik.Windows.Documents.FormatProviders.ReplaceStyleNameHandler.Replace(ReplaceStyleNameContext context) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfStyleImporter.DoVisitText(RtfText text) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfElementIteratorBase.VisitElement(RtfElement element, Boolean recursive) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfElementIteratorBase.VisitGroupChildren(RtfGroup group, Boolean recursive) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfStyleImporter.ImportStyleGroup(RtfGroup group) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfStylesTable.FillStyle(RtfGroup group, StyleType type, Boolean isDefault) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfStylesTable.DoVisitGroup(RtfGroup group) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfElementIteratorBase.VisitElement(RtfElement element, Boolean recursive) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfElementIteratorBase.VisitGroupChildren(RtfGroup group, Boolean recursive) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfStylesTable.ReadTable(RtfGroup group, RtfImportContext context) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfHandlers.RtfGroupHandlers.StylesTableHandler(RtfGroup group, RtfImportContext context) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfDocumentImporter.DoVisitGroup(RtfGroup group) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfElementIteratorBase.VisitElement(RtfElement element, Boolean recursive) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfElementIteratorBase.VisitGroupChildren(RtfGroup group, Boolean recursive) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfDocumentImporter.ImportRoot(RtfGroup rtfGroup) at Telerik.Windows.Documents.FormatProviders.Rtf.Import.RtfDocumentImporter.Import(Stream input, RtfImportSettings settings) at Telerik.Windows.Documents.FormatProviders.Rtf.RtfFormatProvider.Import(Stream input) at Telerik.Windows.Documents.FormatProviders.Rtf.RtfFormatProvider.Import(String input) Fix available in LIB Version 2018.3.924.
When a data provider is used, the designer does not show the RadRichTextBox content, that is shown with no problem at run time.
Workaround: The issue is with finding the format provider used by the data provider. This issue appears at design time only. The workaround is to manually set the format provider of the data provider:
<telerik:HtmlDataProvider
x:Name="htmlDataProvider"
RichTextBox="{Binding ElementName=radRichTextBox, Mode=OneWay}"
Html="<h1>Header3</h1>">
<telerik:HtmlDataProvider.FormatProvider>
<telerik:HtmlFormatProvider />
</telerik:HtmlDataProvider.FormatProvider>
</telerik:HtmlDataProvider>
Whenever the focus is on RadRichTextBox, the keyboard is displayed with Uppercase by Default. After inputting 2-3 characters in uppercase, it changes to lowercase and then alternates between uppercase and lower per character.
Import description lists: <dl>, <dt>, <dd> tags. Possible way for implementation is with paragraphs with left margin.
When a separate file for setting the xaml styles is used and then this file is merged in App.xaml the style cannot be found. As a workaround merge the resources directly in the App.xaml. Fix available in LIB Version 2018.3.1029.
When a new document is created and GetStatisticsInfo is called on it, a NullReferenceException is thrown.
The issue is a regression introduced with another fix, released in R2 2018.
Some of the formatting symbols (e.g. space, tab) don't affect the height of the paragraph. With the current implementation, changing the font size of a formatting symbol, which is first in the paragraph, changes its height as well.
With a picture of original size like this : width 2 800 and Height 1376. On the screen the picture is around 470 by 230. If I go to the Image Editor, it shows me the picture size itself but not the area size used by the picture. It is a good thing to have the original picture's dimension but we work with the dimension used in the document. So, could you do something to resize the picture used in the document.
In my samples, you'll see my picture in a document (ie1), what I see when I go in the Image Editor (ie2) and, when I go to the Resize section (ie3). Suggestion, put the original image's dimension on the top of the right corner in the resize section. The width and Height should show the dimension in the document.
Thanks a lot,
Nested ol/ul list should be inside a <li> element of the list in which it is nested. For example:
<ul>