Completed
Last Updated: 13 Mar 2024 09:45 by ADMIN
Release 2024.1.130 (2024 Q1)
Created by: Felix
Comments: 0
Category: SyntaxEditor
Type: Feature Request
4
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.
Unplanned
Last Updated: 22 Nov 2023 14:33 by Richard
Created by: Petar
Comments: 4
Category: SyntaxEditor
Type: Feature Request
11
Add dependency property for showing/hiding the line numbers on the left of the source code.
Unplanned
Last Updated: 03 Nov 2023 09:23 by Stenly
We could introduce API for customizing the folding region lines and their respective regions. For example, a customization could be hover-coloring of line regions, like in the latest VS:

Duplicated
Last Updated: 25 Sep 2023 07:06 by ADMIN
Created by: Petar
Comments: 0
Category: SyntaxEditor
Type: Feature Request
0
Add support for successful typing text with IME - Chinese, Japanese, Korean etc.
Currently there are input issues, selection issues, caret issues when using IME input.
Completed
Last Updated: 13 Jul 2023 08:43 by ADMIN
Release R2 2023 SP1
Created by: Martin Ivanov
Comments: 0
Category: SyntaxEditor
Type: Feature Request
1

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

Completed
Last Updated: 27 Apr 2023 07:51 by ADMIN
Release R2 2023

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

Completed
Last Updated: 08 Sep 2022 15:41 by ADMIN
Release R3 2022
Created by: Petar
Comments: 1
Category: SyntaxEditor
Type: Feature Request
21
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.
Completed
Last Updated: 29 Jun 2022 07:24 by ADMIN
Release LIB 2022.2.704 (04 July 2022)
Expose API to control the FontWeight and FontStyle of the highlighted words.
Unplanned
Last Updated: 06 May 2022 10:57 by Stenly
Created by: Stenly
Comments: 0
Category: SyntaxEditor
Type: Feature Request
2
Currently, the RadSyntaxEditor control does not have an out-of-the-box printing functionality.
Unplanned
Last Updated: 02 May 2022 11:58 by Greg
Created by: Stenly
Comments: 1
Category: SyntaxEditor
Type: Feature Request
1
Add functionality for precise positioning of the popups inside the RadSyntaxEditor control.
Completed
Last Updated: 31 May 2021 08:01 by ADMIN
Release LIB 2020.2.406 (04/06/2020)
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. 
Declined
Last Updated: 17 May 2021 12:42 by ADMIN
Created by: Robby
Comments: 1
Category: SyntaxEditor
Type: Feature Request
0

Default keystroke in other editors to activate text replacement is: ctrl+H

Would be nive to enable this in the syntax editor.

 

Unplanned
Last Updated: 20 Apr 2021 11:12 by ADMIN
Created by: Robby
Comments: 1
Category: SyntaxEditor
Type: Feature Request
2

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.

Completed
Last Updated: 08 Dec 2020 14:43 by ADMIN
Release LIB 2020.3.1214
Created by: Petar
Comments: 0
Category: SyntaxEditor
Type: Feature Request
10

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.

Completed
Last Updated: 04 Nov 2020 16:03 by ADMIN
Release LIB 2020.3.1109 (11/09/2020)
Created by: Andrea.Gasparini
Comments: 0
Category: SyntaxEditor
Type: Feature Request
3
Expose a property to control the width of the search panel as the buttons may get clipped if their text is too long.
Completed
Last Updated: 01 Jul 2020 10:19 by ADMIN
Release LIB 2020.1.302 (02/03/2020)
Introduce a property to control whether the matching of the start and end folding tags is case sensitive or not.
Unplanned
Last Updated: 30 Jun 2020 11:52 by ADMIN
Currently, if you load a big .xml file with big number of tags, the XmlFoldingTagger takes a lot of time to execute its logic. Improve the performance in those situations.
Completed
Last Updated: 30 Apr 2020 06:46 by ADMIN
Release R2 2020
Currently the strings are not colored in C#, VB, JS documents working with CSharpTagger, JavaScriptTagger, VisualBasicTagger. Make the strings colored out of the box.
Unplanned
Last Updated: 13 Feb 2020 14:00 by ADMIN
Created by: Troy
Comments: 1
Category: SyntaxEditor
Type: Feature Request
2

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
---- - It looks like that the tagger is only looking for 2 – only. If there are more than 2 in sequence, it doesn’t identify it as a comment and should
Unplanned
Last Updated: 28 Jan 2020 12:27 by ADMIN
We could create intellisense similar to Visual Studio.
1 2