Entrian Solutions

Archive for February, 2017

Entrian Source Search 1.7.5: Performance and responsiveness

Thursday, February 23rd, 2017 by Richie Hindle

I’m very happy to announce Entrian Source Search 1.7.5, with these features and fixes:

  • Searching now happens in a background thread, with a Stop button.  Accidentally searching for a semicolon no longer locks up Visual Studio for a few seconds.  🙂  Thanks, Jeremy.
  • Improved performance of multi-token wildcards in cases where the query includes two or more of them.
  • Removed an unnecessary lock between the indexer and the searcher, which meant that searches could take longer than necessary when indexing was happening.
  • The number of hits is now limited to one million, because once you get into multiples of that, Visual Studio tends to run out of address space and crash.  (This involved adding my favourite class of the week, the OneMeeellionHitsException. 🙂 )
  • The text in the Search box is now clearly visible on High DPI displays (broken by query syntax highlighting in the previous version).  Thanks, Hans-Peter.
  • The query syntax highlighting colors are now more visible in dark themes.
  • The Home and Left keys now work when you have a query text selection that ends at far left of the query (also broken by query syntax highlighting).
  • Search warnings (eg. “Per-line wildcards not fully ready: Update incomplete”) are now printed by the command-line search tool (ess.exe).
  • Made the Search box wider when the display is wide enough for it.

You can download this new version from the download page or the gallery.


Entrian Source Search 1.7.4: Multi-token wildcards; query and result coloring

Wednesday, February 15th, 2017 by Richie Hindle

I’m very pleased to announce Entrian Source Search 1.7.4, which comes with a pile of cool new features:

  • Multi-token wildcards.  There are now three kinds of wildcards:
    1. Single-token wildcard: wild* – the asterisk is next to an alphanumeric character, and expands to a single token, eg. wild, wildcard, wilderness. Asterisks in a single-token wildcard can appear *any*where* in the word. (Source Search has supported this type of wildcard since 2008.)
    2. Single-line multi-token wildcard: this * that – the asterisk is on its own, and matches any number of tokens on the same line.
    3. Multi-line multi-token wildcard: this *:10 that – rather than being limited to a single line, these wildcards are explicitly limited to a number of tokens, and can span multiple lines.

    Here’s how you might find all the std::vectors concerning selections:

    Thanks, Chris and Vincent.

  • Query syntax coloring, and results coloring: in the Search box, positive filters are now shown in green text, negative filters are shown in red text, and multiple search phrases are shown with different colored backgrounds with matching colors in the results list.

    Here’s how you might find the places where your Python code uses a list or a dict as the default value for a function parameter:

    Thanks, Chris.

  • In the results list, the line numbers for lines with multiple matches (via the “Work like grep” option) now tell you how many matches there are on the line:
  • Source Search now displays syntax highlighting for both Python and PHP source files in the results list.  Thanks, Patrice.(Note: Python and PHP syntax coloring will only be present after the relevant files are re-indexed; that will happen automatically when you start up this version of Source Search.)
  • The Ctrl+Alt+C shortcut key in the results list or the search box copies the result list to the clipboard as text.  Thanks, Anders.
  • Ctrl+Del in the Search box does delete-word-forward.  Thanks, Dylan.
  • The existing Ctrl+H and Ctrl+L shortcuts for History Back and History Forward now appear in the tooltips.  Thanks, Martin.
  • The match-highlight background rectangles in the results list no longer escape their bounds and paint over the other columns when “Work like grep” is enabled and the results list is narrow.

You can download this new version from the download page or the gallery.


Entrian Inline Watch 1.0.5: Bugfix for popups on High DPI displays

Wednesday, February 15th, 2017 by Richie Hindle

I’m pleased to announce Entrian Inline Watch 1.0.5, which fixes a bug:

  • A popup value, shown on a High DPI display, could wander across the screen when the value it was displaying changed.  Thanks, Martin.

The new version is available from the download page or the gallery.


Entrian Source Search 1.7.3: General usability enhancements

Friday, February 3rd, 2017 by Richie Hindle

I’m very pleased to announce Entrian Source Search 1.7.3, with this pile of fixes and features:

  • Where your query matches only one result, it’s now optional whether to automatically open that result.  You can control this independently for text searches and for filter-only searches like file:renderer.  Thanks, Peter.
  • The way the history works is improved.  Search for A then B then C, go Back, Back, Search (for A), search for D, then go Back.  You now see A rather than C.  Previously, every time you searched for something new, it then took longer and longer to return to A, B, etc.  Now, searches that come from the history are promoted to the end.  (But note that going Back, Search, Back, Search, Back, Search will still go C, B, A.)  Thanks, Chris.
  • Source Search now copes better when it hits an unexpected file system exception.  These can be caused by (for example) network drives going offline, shared indexes being deleted, or indexes being corrupted by Visual Studio crashes or power failures.  Previously, these situations could make Source Search crash.  Now, you’re asked whether to ignore the error and continue (maybe because a network share went away for a moment and is now back again), temporarily disable Source Search, or send in a crash report:
  • You can now re-enable Source Search after a crash, without restarting Visual Studio, using the “More / Enable…” command.
  • Fixed a crash when the option to “Work like grep: show one result line per source line” is enabled and there are multiple overlapping results on a single line (eg. searching for a.a where the source contains a.a.a).
  • Source Search once again works on machines with FIPS compliance enabled.  (Deja vu? Yes, I fixed this in January 2013, but it crept back in).
  • Improved memory usage, reducing the chances of an OutOfMemoryException.  Thanks, Fred.

As always, the upgrade is available for free to all licensed users, and as a 30-individual-day trial for everyone else.  You can download it from the download page or the gallery.