Html export of RadRichTextBox to perform font-size export in different units. Case 2: If you export a document using the HtmlFormatProvider, all style properties which contain measurement units are exported in pixel units. This makes the exported documents look much smaller when opened on devices with higher pixel density. WORKAROUND: use Regex to find, convert and replace the font-size attributes HtmlFormatProvider html = new HtmlFormatProvider(); string res = html.Export(document); Regex regex = new Regex(@"font-size: [0-9]*\.?[0-9]*px"); Match match = null; do { match = regex.Match(res); if (!match.Success) { break; } string value = match.Value.Substring("font-size: ".Length, match.Value.Length - "font-size: ".Length - "px".Length); double pts = double.Parse(value) * 72 / 96; res = res.Replace(match.Value, @"font-size: " + Math.Round(pts, 4) + "pt"); } while (match.Success); File.WriteAllText("output.html", res);
RadRichTextBox large txt documents (20000 rows)are loaded very slowly.
To reproduce: add some text to RadRichTextEditor and set the Enabled property to false. You will notice that the text gets bold and blurry. Workaround: instead of disabling RadRichTextEditor, use the ReadOnly property.
Provide functionality allowing a document to be thumbnailed. The customers should be able to export a document to an image. Workaround: Use attached project.
RadRichTextBox - add import from PDF file.
Implement commands and UI for producing labels using Mail Merge. Behind the scenes this is implemented as Table with the proper number of table columns and rows, and eventually (depending on the setup) NEXT field (https://support.office.com/en-us/article/Field-codes-Next-field-3862fad6-0297-411a-a4e7-6ff5bcf178fd?ui=en-US&rs=en-US&ad=US) - so this will eventually require implementing NEXT field. Note: In MS Word, this is in Mailings -> Start Mail Merge -> Labels...
Workaround: public class MyInputBehavior : InputBehavior { public MyInputBehavior(DocumentView view) : base(view) { } public override bool ProcessKeyPress(System.Windows.Forms.KeyPressEventArgs e) { // TO DO: You code here e.KeyChar = char.ToUpper(e.KeyChar); return true; // By commenting the base call you are supresing the default logic //return base.ProcessKeyPress(e); } } Then you should replace the default input behavior by using the following code snippet: this.richTextBox.DocumentView.InputBehavior = new MyInputBehavior(this.richTextBox.DocumentView);
The customers need to convert the position to an integer number representing the offset of the current position from the first position in the document. A method returning the position at a specified offset would be useful as well.
Some voice recognition software (Nuance) is using integer positions as well.
In MS Word, MS RichTextBox and DevExpress RichTextBox, the positions are represented as integer numbers.
How to reproduce: private void radButton1_Click(object sender, EventArgs e) { RadPrintDocument doc = new RadPrintDocument(); doc.Margins = new Margins(0, 0, 10, 10); doc.AssociatedObject = this.radRichTextEditor1; RadPrintPreviewDialog dialog = new RadPrintPreviewDialog(); dialog.Document = doc; dialog.ShowDialog(); } Workaround: apply the margins on the document loaded in the editor private void radButton1_Click(object sender, EventArgs e) { RadPrintDocument doc = new RadPrintDocument(); this.radRichTextEditor1.Document.SectionDefaultPageMargin = new Telerik.WinForms.Documents.Layout.Padding(0, 0, 10, 10); doc.AssociatedObject = this.radRichTextEditor1; RadPrintPreviewDialog dialog = new RadPrintPreviewDialog(); dialog.Document = doc; dialog.ShowDialog(); }
When you have more than one RadRichTextEditor controls on the form and you have selected text in both of theme, only the focused RadRichTextEditor should show the selection.
How to reproduce: create a table with 1px of the inner borders and 3px of the outer borders. The attached screenshots demonstrates the issue. A similar result can be also observed with other widths as well.
- There should be a formatting symbol for the character - Pressing Ctrl+Shift+Space should insert the character (standard MS Word shortcut) - Import from docx should be implemented - The symbol should be treated as a separator between words when spell-checking