Skip to main content

Bug fixes concerning tabs and syntax highlighting

The tab spacing bug

This problem stems from a bug in the RichTextBox. Basically, the tab spacing in the RichTextBox is inconsistent and very strange. Sometimes a tab will be bigger than a space, and sometimes it'll be smaller than a space. I have informed Microsoft of the bug and I'm hoping they'll fix it for Silverlight 5.

What this means for Regex Hero is that tabs would throw the highlighting out of alignment. So my fix was to override tabs with spaces. I had made this change weeks ago. But today's release has this same treatment on pasting tabbed text.

This isn't ideal and basically means the \t regular expression will never match anything in Regex Hero. If I can find a better workaround I will do it. But at least today's fix means that the yellow highlighting will always be in alignment and is reliable again.

To help ensure Microsoft fixes this bug in the RichTextBox in a timely manner, you can help by up-voting the bug here on MS Connect.

Syntax highlighting

The syntax highlighter had a minor bug with back slashes. The following regular expressions are valid, but the syntax highlighter was painting them red...


It was seeing the \ before the ending parenthesis, escaping the parenthesis, and then thinking that these constructs were not closed. It didn't look far enough back to see the \\. So I fixed the bug, and now it works properly.


Popular posts from this blog

Regex Hero for Windows 10 is Underway

Awhile back I began working on an HTML5 / JavaScript version of Regex Hero . However, it was a huge undertaking essentially requiring a complete rewrite of the entire application. I have not had enough time to dedicate to this lately. So I've begun again, this time rewriting Regex Hero to work in WPF. It'll be usable in Windows 10 and downloadable from the Microsoft Store. This is a much easier task that also has the advantage of running the .NET regex library from the application itself. This will allow for the same speedy experience of testing your regular expressions and getting instant feedback that Regex Hero users have always enjoyed. I expect the first release to be ready in Q4 of 2019.

Optimizing Your Regular Expressions

Regular expressions will backtrack.  That's an unfortunate thing about them because backtracking can be slow.    And in certain (rare) cases the performance can become so awful that executing the regular expression against a relatively short string could take over a minute.  There's a good article about catastrophic backtracking over at . And today I created a video about all of this called  Regex Lesson 5: Optimization .  In the video I start with a very poorly written regular expression and make several improvements to it, using the benchmarking feature along the way.  By the end of the video I make the regular expression over 3 million times faster. In addition, today's update to Regex Hero provides a little message in the event that you encounter a regular expression that takes over 10 seconds to evaluate... And then last of all, I changed the benchmarking feature a bit.  In the past it would simply test your regular expression against

Silverlight 4 Coming in April, or Maybe Sooner

The exact release date has not been announced. But Visual Studio 2010 RTM is coming out in April and I think it's safe to assume that Silverlight 4 will be released no later than that. Each release of Silverlight has brought massive improvements over the previous version. And once again, Silverlight 4 does not disappoint. There is a long list of improvements but the ones that I think that will affect Regex Hero are as follows: RichTextBox My plan is to use this in place of all 4 major textboxes in Regex Hero. The new RichTextBox has built-in multiple undos & redos, so I can ditch my home-brewed code. It should be nice to use for syntax highlighting for the regular expressions I intend to create. It also has a built-in API to determine the pixel position of the text. I should be able to use this API and build a new highlighting scheme based off of it. This should do a couple things. First, I should be able to finally fix the problem I had with the ScrollViewer and