I am making a simple text and script editor with code highlighting. For that I use a RichTextBox. But I don't know how to make it show the lines' numbers on the left side, like in VS or Notepad++. Is there any solution?
I would store each line in a class which has methods to publish to the richtextbox. In that method, you could prepend the line number based on its position in the class.
For example (very roughly):
class myText
{
public List<string> Lines;
public string GetList()
{
StringBuilder sb = new StringBuilder();
int i = 0;
foreach (string s in Lines)
{
sb.AppendFormat("{0}: {1}", i, s).AppendLine();
i++;
}
return sb.ToString();
}
}
Examples:
Line Numbers for RichText Control in C#
Line Numbering of RichTextBox in .NET 2.0
Numbering lines of RichTextBox in .NET 2.0
LineNumbers for the RichTextBox
I tried re-using the code from the codeproject articles referenced elsewhere, but every option I looked at, seemed a bit too kludgy.
So I built another RichTextBoxEx that displays line numbers.
The line numbering can be turned on or off. It's fast. It scrolls cleanly. You can select the color of the numbers, the background colors for a gradient, the border thickness, the font, whether to use leading zeros. You can choose to number lines "as displayed" or according to the hard newlines in the RTB.
Examples:
It has limitations: it displays numbers only on the left. You could change that without too much effort if you cared.
The code is designed as C# project. Though it's part of a larger "solution" (an XPath Visualization tool), the custom RichTextBox is packaged as a separable assembly, and is ready to use in your new projects. In Visual Studio, just add a reference to the DLL, and you can drag-and-drop it onto your design surface. You can just discard the other code from the larger solution.
Scintilla.Net http://scintillanet.codeplex.com/ could be the most feasible solution for your needs. But for my project I used solution suggested by Cheeso (RichTextBoxEx from XPath visualizer). It's simple and fast enough for not very big documents. All other .net components from the internet were incredibly slow.