Localize the tooltips for the match case button, the match word button and the use regular expression button.
Currently, the tooltips of the buttons are using hardcoded strings in English.
To translate the tooltips, you can get the corresponding buttons on load of the syntax editor control and replace their tooltips manually.
private void syntaxEditor_Loaded(object sender, RoutedEventArgs e)
{
var buttons = this.syntaxEditor.ChildrenOfType<RadToggleButton>();
var matchCaseButton = buttons.FirstOrDefault(x => x.Name == "PART_MatchCaseButton");
var matchWordButton = buttons.FirstOrDefault(x => x.Name == "PART_MatchWordButton");
var useRegularExpressionsButton = buttons.FirstOrDefault(x => x.Name == "PART_UseRegularExpressionsButton");
matchCaseButton.ToolTip = CreateToolTip("SyntaxEditor_MatchCase"); // these are custom localization resource keys that should be manually defined by the developer that uses this solution
matchWordButton.ToolTip = CreateToolTip("SyntaxEditor_MatchWord");
useRegularExpressionsButton.ToolTip = CreateToolTip("SyntaxEditor_UseRegularExpressions");
}
private static ToolTip CreateToolTip(string resourceKey)
{
var toolTip = new ToolTip();
toolTip.Content = LocalizationManager.Manager.GetStringOverride(resourceKey);
return toolTip;
}
Single line folding regions is falsely recognized (by default it should be avoided) and messes up with outer regions.
For example
1 [
2 [ inner region]
3]
There should be no folding button on the inner line. Collapsing line 1 does not collapse 3 but only 1 and 2 which is wrong.
When using LineHighlightTagger a NullReferenceException is thrown. To workaround this exception, you can add a custom TextFormatDefinition object to the TextFormatDefinitions collection of the RadSyntaxEditor.
this.syntaxEditor.TextFormatDefinitions.AddLast(LineHighlightTagger.LineHighlightFormatDefinition, new TextFormatDefinition(new Telerik.Windows.Controls.SyntaxEditor.UI.Pen(new SolidColorBrush(Colors.Gray), new Thickness(1))));
Shift + Alt + Down Selection then typing multiple characters results in all of them being typed in all selected lines.
Shift + Alt _ Down Selection then typing multiple characters results in only the first one being typed in all lines, then selection is lost and next chars are inserted in the last selected line only.
//using System;
//usign System.Windows.Controls;
Two consecutive lines with commented using sections result in ArgumentOutOfRangeException in SyntaxEditor with CSharpFoldingTagger.
/* and */ words are start /end words for multiline comments in C#/SQL/VB
They should be outside strings when they form a comment block.
Character data sections are not recognized and colored by the XmlTagger in SyntaxEditor.
Visual Studio:
SyntaxEditor:
Also parsing such elements is wrong:
Expanded OK:
Collapsed BUG (Node is closed but it shouldnt):
issue 2 - single line CDATA does not need folding button
Good morning,
can You implement in one of the next releases the regex and case sensitive search? I provided you the Visual Studio 2019 search screenshot
When the variation is changed in the VisualStudio2013 theme, the Foreground is not updated.
As a workaround, you can reset the Template of the control:
var template = this.syntaxEditor.Template;
this.syntaxEditor.Template = null;
this.syntaxEditor.Template = template;
After putting a folding region out of the viewport by scrolling and then bringing it back, the folding region is not drawn correctly when typing new lines into it.
In some scenarios, an ArgumentException is thrown when a folding region with selected text is collapsed. An example can be seen below: