The IsBusy property of RadBusyIndicator does not correctly reflect the value of its data-bound source when the control is unloaded and then loaded again while using a OneWay binding.
A common scenario where this occurs is when RadBusyIndicator is hosted inside a TabItem of a TabControl:
The binding is not re-evaluated when the control is loaded again, resulting in the control displaying a stale value that is out of sync with the bound ViewModel property.
Borders can overhang 1 px from the corresponding cells. The issue is reproducible only on some zoom levels, and is most probably related to WPF layout rounding. The issue is mostly visible when borders are missing. On different zoom levels, different borders are hanging.
Clicking on floating Image when the caret position is not in the viewport, changes the viewport and starts image dragging. Instead, the image should just be selected. Steps to reproduce: 1. Start with empty document 2. Insert image, make it floating (right-click on it, select Text Wrapping -> In Front Of Text) 3. Drag the image near the bottom of the document. 4. Scroll and, if needed, zoom to such a factor, so that the first paragraph is outside of the view port. 5. Select the image (keep in mind that the image shouldn't be selected - the position should be at some of the previous paragraphs) Observe: The image dragging adorner is visible and the viewport is changed. Expected: The behavior shall be the same as MS Word - the viewport shouldn't be changed, and the image should just be selected
When floating image is added to empty table cell, it is positioned in a way that overlaps the table border.
GoToPage() method is not working correctly in some cases when called in DocumentChanged event handler. The known cases are described below:
1. When RadPdfViewer and the document are loaded initially and document is set through the RadPdfViewer.Document property.
Workaround: DocumentSource property could be set (in XAML or in code-behind) instead of the Document property. If the Document property is used, this should be done after RadPdfViewer is loaded.
2. When the ScaleMode is changed in DocumentChanged event handler and then GoToPage() method is called in the same event handler.
When inserting text (document fragment) next to a correctly spelled word they get both underlined as incorrect.
Currently when the text contains consecutive non-space symbols like "~!@#$%^&*()_+=-`[]{};:'"/\|., ", each character is detected as a separate word. Instead, they should be considered one word, including all the subsequent space characters.
The following functionalities should respect this grouping:
- Caret navigation by words (CTRL + left/right arrow), MoveCaret UI command and the corresponding DocumentPosition methods.
- Selecting word by double clicking.
'Decrement paragraph left indent' command can set negative left indent which makes bullets/numbering of a list clipped. Instead, it shouldn't be executed if the bullets/numbering would become invisible.
Workaround: Cancel the command in CommandExecuting event:
this.radRichTextBox.CommandExecuting += (sender, e) =>
{
if (e.Command == this.radRichTextBox.Commands.DecrementParagraphLeftIndentCommand)
{
if (this.radRichTextBox.Document.Selection.GetSelectedParagraphs().Any(p => p.IsInList && p.LeftIndent <= 24))
{
e.Cancel = true;
}
}
};
The spacing between the letters is too big.
The built-in Hyperlink style is not applied to hyperlinks imported from HTML (<a> tag). As a result, the hyperlinks in the document do not have the blue underline.
Workaround: Subscribe for the SetupDocument event of the HtmlDataProvider and set the hyperlinks' style manually.
private void HtmlDataProvider_SetupDocument(object sender, Telerik.Windows.Documents.FormatProviders.SetupDocumentEventArgs e)
{
StyleDefinition hyperLinkStyle = e.Document.StyleRepository[RadDocumentDefaultStyles.HyperlinkStyleName];
hyperLinkStyle.SpanProperties.ForeColor = Colors.Green;//Color.FromRgb(0xff, 0x7a, 0xcc);
var hyperlinks = e.Document.EnumerateChildrenOfType<HyperlinkRangeStart>();
RadDocumentEditor editor = new RadDocumentEditor(e.Document);
editor.Document.History.IsEnabled = false;
foreach (HyperlinkRangeStart hyperlink in hyperlinks)
{
e.Document.Selection.SelectAnnotationRange(hyperlink);
editor.ChangeStyleName(RadDocumentDefaultStyles.HyperlinkStyleName);
}
e.Document.Selection.Clear();
editor.Document.History.IsEnabled = true;
}
If there are two words with two spaces between them, and between the spaces there is annotation with SkipPositionBefore = false (e.g. track changes revision annotation or comment), and current editing style is changed on the position between the spaces (i.e. Toggle Bold, for example, without selection present) the first word formatting is affected (e.g. it becomes bold). Steps to reproduce: Variant 1: - Insert two words with a single space between them (e.g. "text telerik") - Turn Track Changes On - Insert a space after the single space between the two words. (i.e. right before 'telerik') - Toggle Bold Observe: "text" gets bold. Expected: "text" doesn't get bold, just current editing style is changed. Variant 2: - Insert two words with a two spaces between them (e.g. "text telerik") - Select the second space and the second word, and insert comment. - Put the caret between the spaces. - Toggle Bold Observe: "text" gets bold. Expected: "text" doesn't get bold, just current editing style is changed.
TabStopsProperties dialog is non-modal dialog, but it should be modal.
workaround:
public MainWindow()
{
InitializeComponent();
this.grid.Loaded += grid_Loaded;
}
void grid_Loaded(object sender, RoutedEventArgs e)
{
this.grid.ChildrenOfType<Grid>().FirstOrDefault(x => x.Name == "PART_OuterGrid").RowDefinitions[1].Height = GridLength.Auto;
var cells = this.grid.ChildrenOfType<GridViewHeaderCell>();
foreach (GridViewHeaderCell cell in cells)
{
cell.ChildrenOfType<Grid>().FirstOrDefault(x => x.Name == "PART_OuterGrid").RowDefinitions[1].Height = GridLength.Auto;
}
}
Reproducible in the latest demo. Create daily recurrence. Select multiple occurrences and drag them. For the first time they will be dragged. Then select exceptional (this is important!) occurrences and drag them - only the occurrence which was selected first will be dragged.
When a RadBitmap is rotated to degrees for which sine and cosine are not integers (every angle which is not 90, 180, 270 or 360) applies wrongly calculated transformations and the bitmap' size is no longer correct. For example, rotating a bitmap to -30 and then to 30 degrees changes its size.