Add ability to disable horizontal scrollbar and enable word wrapping - fixed width of editor and if the word cannot fit - it is moved to next line.

Adding breakpoints (markers) to particular lines in code should be possible.

Should be doable via UI or in code. Collection of all breakpoints should be accessible in code too.

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

Currently the Caret of the SyntaxEditor does not behave like Caret in MS TextBox/ RichTextBox when IME is opened - IME opens on the bottom right part of the screen instead of below the caret. Also some input issues when selection is done in the IME should be addressed for a full support of this feature.

Add separate folding tagger class for creating folding (collapsible) regions in XML, XAML, HTML code files.

Hello,

When we resize the syntaxEditor control, the folding buttons moved. You can reproduce this isssue in your demos.

 

1. Reduce the contents of the sample
2. Increase the size of sample window and see the buttons are not besides the line

 

Best regards,

Expose a property to control the width of the search panel as the buttons may get clipped if their text is too long.

The GotoLine method is not implemented

For example "//====" will not be commented in C#. 

If you have an XML attribute with a string value, but the value is not fully rendered into the viewport, its color defaults to black, instead of the expected blue color.

To work this around, you can create a custom XmlTagger and override its GetTags() method. This will allow you to properly catch the string value and return it as a tag span element with its ClassificationType set to "string".

A message could be shown when using the Find mechanism, and you reach the end of the file or the starting point of the search. 

Introduce a property to control whether the matching of the start and end folding tags is case sensitive or not.

If secondary wpf window is opened in an application, the enter key does not work in SyntaxEditor. It does not produce new line as expected.

Currently the strings are not colored in C#, VB, JS documents working with CSharpTagger, JavaScriptTagger, VisualBasicTagger. Make the strings colored out of the box.

When the control is inside ScrollViewer and you click it, focus is lost and caret disappears. Some controls have built in ScrollViewer , for example LayoutControl so placing the editor in LayoutControl also leads to the same issue.

Generally placing the syntaxeditor in scrollviewer is risky for the vertical virtualization so at least a height should be set to the control. In R2 2020 SP, an exception will be thrown if Syntax Editor with no height is added in scroll viewer or stack panel or other panel which measures vertically with infinity.

Workaround for this issue:

        private void syntaxEditor_MouseLeftButtonDown(object sender, MouseButtonEventArgs e)
        {
            e.Handled = true;
        }

In some scenarios, an ArgumentException is thrown when a folding region with selected text is collapsed. An example can be seen below:

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.

The highlighting of tags becomes invalid when scrolling horizontally.

/* and */ words are start /end words for multiline comments in C#/SQL/VB 

They should be outside strings when they form a comment block.

Big text with many lines or lines long enough to cover the viewport height when wrapped with word wrapping break the virtualization mechanism in RadSyntaxEditor. This makes the scrolling and resizing performance slow.