The unit that is used by default is px. Allow modification to the default unit, say pt.
RadRichTextBox.TabIndex property does not have effect. The TabIndex will remain at maximum and RadRichTextBox will be last in the tab order. Moreover, setting RadRichTextBox.IsTabStop to false also doesn't have effect. The issue is showstopper for the cases where RadRichTextBox is used along with other controls.
If a table style is applied to a table, and then document is exported/imported to RTF, properties of the style are applied as local properties. Subsequent edits of the style (or changing the style of the table) seems to not work, as the local properties are with higher priority.
- When a floating image is inserted into header/footer the image is clipped. However, if Enter is pressed in the header/footer later, the whole image is shown. Further, if Enter is pressed again, the image is clipped again. - When floating images are placed in a header or footer, and are positioned outside of the text editor's area, they are not visualized. MS Word visualizes such images as slightly grayed out (similar to watermarks) in normal mode, and always visualizes them in Header/Footer edit mode.
Workaround: We have prepared an SDK example which demonstrates how to import .doc files in RadRichTextBox using third-party library. The sample could be found in our SDK repository in Github at the following link: https://github.com/telerik/xaml-sdk/tree/master/RichTextBox/DocFormatProviderDemo
RadRichTextBox should have API allowing to set which user can accept or reject the changes. Currently all users can do this.
private void radRichTextBox_CommandExecuted(object sender, CommandExecutedEventArgs e)
{
if (e.Command is DeleteCommand && imageToDelete!=null)
{
this.radRichTextBox.Document.Selection.Clear();
this.radRichTextBox.Document.Selection.AddDocumentElementToSelection(imageToDelete);
this.radRichTextBox.Delete(true);
this.imageToDelete = null;
}
}
private ImageInline imageToDelete;
void radRichTextBox_CommandExecuting(object sender, Telerik.Windows.Documents.RichTextBoxCommands.CommandExecutingEventArgs e)
{
if (e.Command is DeleteCommand)
{
var selectedBoxes = this.radRichTextBox.Document.Selection.GetSelectedBoxes().ToList();
if (selectedBoxes.Count() == 2 && selectedBoxes[0].AssociatedInline is FieldRangeStart && selectedBoxes[1].AssociatedInline is ImageInline)
{
imageToDelete = selectedBoxes[1].AssociatedInline as ImageInline;
}
}
}
We noticed that the RadRichTextBox for WPF is not working correctly Windows Narrator or JAWS screen readers. As a result, due to Section 508 compliance, this prevents government clients from using our software. We have tried three different computers with Windows 7 with Windows Narrator and JAWS 15.0.10026. Both Windows Narrator and JAWS speak all the controls in our application except for the RadRichTextBox. Type a few lines in the editor then up, down, left, and right arrow through the text. We do not hear the character echo when performing left and right arrow. We do not hear the entire line of text spoken when performing up and down arrow. When I try this in the RadRichTextBox control, using our test application, using JAWS, I hear the window title "Telerik Test App" when I peform an up and down arrow. Also, when I perform left and right error I hear the letter "T" which I believe is the first letter in the window title. When I try this in the RadRichTextBox control, using our text application, using Windows Narrator, I hear "up arrow" and "down arrow" when I peform an up and down arrow. Also, when I perform left and right error I hear "left arrow" and "right arrow."
When a symbol is inserted, the font family of RichTextBox is set to the symbol's font family. Workaround: Create a custom InsertSymbolDialog. The font family could be persisted in the Show() method of the new dialog and reset when the dialog is closing. Attached is a sample project demonstrating the workaround.
Currently saving to an .rtf document with footnotes strips the footnotes and endnotes.
This property allows the user to set the transparency of the image watermark. In the OOXML, the property is written using the 'blacklevel' attribute of the image.
The fix is available in our LIB release (v. 2015.3.1123).
The following parts are with hard coded strings and cannot be localized: - Insert Caption (InsertCaptionDialog): Combo boxes for label and separator - Paragraph Properties (ParagraphPropertiesDialog): Units of spacing and indentation values (pt) - Tab Stops Properties (TabStopsPropertiesDialog): The text of the tabStopsToBeClearedTextBloc - Cross references: reference types Figure and Table - TOC and TOF: Heading and Figure, Caption labels - Document Ruler: Tooltips - FormattingColorPicker: The "No Color" string Available in R1 2018 SP2 Release Version.
Add support for math type equations.