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.

Hello,

We would like to use SyntaxEditor by providing our own programming language definition. It would be great to have the ability to feed SyntaxEditor with a language definition file. This file could be use an EBNF-like format to provide syntax coloration.

Thanks & regards,

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

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,

I do have some feedback on this component. I love it, but of course there are some areas where improvement can be made. For instance, in the screenshot below, I have highlighted some words where improvement can be made.

1. ‘1,2,3,5’ – Literals in SSMS are Red
2. ‘ER – 100% OF MEDICARE’ – OF is highlighted in Blue. It is contained in a literal and shouldn’t be highlighted
3. ISNULL – Is a function and should be highlighted in Blue

When using XML Tagger, XML Folding tagger with XML text document, the folding tagger freezes the UI while typing.
Generally in Visual Studio, the XML Folding tagger is processed in background while in SyntaxEditor this is done on the UI thread.
Several optimization options might be applied:

    - process xml folding in background

    - process folding similar to process search while typing - a period of inactivity time is needed to invalidate the search / folding

   - caching - if the edit does not change the folding configuration, no processing and redrawing of folding is required

  - some parts for extracting tooltip content and folded content should be optimized

We want to have the option to replace texts only in a selected part of the document. 

Use Notepad++ as a reference to check this feature.

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;
}