I’m pleased to announce Entrian Inline Watch 1.0.4, with two enhancements and a restriction:

• Now supports Visual Studio 2017.
• (Edit:) No longer supports Still supports Visual Studio 2010, but via a separate download.
• The “Entrian Inline Watch: Toggle display” menu/toolbar command is now checked when Entrian Inline Watch is enabled.

This new release is available from the download page or the gallery.

I’m pleased to announce Entrian Inline Watch 1.0.3, which fixes three bugs:

• For some users, changing the settings and OK’ing the settings dialog would fail to save the new settings after the first time.  Thanks, Miha and Jordan.
• When debugging with Just My Code enabled, visiting a stack frame other than the top one could display values for a frame above or below the one you were actually looking at.  Thanks, Chris.
• Displaying a long string value containing the substring $& could cause Inline Watch to hang.

This new release is available from the download page or the gallery.

I’ve just released Entrian Inline Watch 1.0.2, which fixes the following howling bug:

• When debugging a Unity C# script with Inline Watch, it could pass the methods calls in your code to the Unity debugging engine to be evaluated.  So if your code contains the line WeaponList.Clear(); and you stepped through the code, Inline Watch would cause that code to be executed at the wrong time, and your WeaponList would be mysteriously cleared.  This is not very good.  Thanks, Martin.

This new release is available from the download page or the gallery, and is a highly recommended update for Unity users!  (Standard .NET debugging with Visual Studio is unaffected.)

I’ve just released Entrian Inline Watch 1.0.1, which fixes the following bugs:

• Values for long strings no longer sometimes gain an extra double-quote character.  Thanks, Martin.
• Where a debugger uses backticks in 64-bit addresses (like the WndDBG engine does) Inline Watch no longer only sees the part before the first backtick.
• Values are now displayed for array lookups that use an expression for the array suffix, eg. a[i+1].  Thanks, Martin.
• Fixed a crash when Visual Studio gets into a state where it can’t access the debuggee’s call stack.  Thanks, Fred.
• Where an accessor or array expression is followed by a semicolon or a comma (like.this();) the value is now displayed in the right place, rather than after the semicolon.  Thanks, Martin.
• Values containing ampersands are now wide enough (gee thanks, TextRenderer.MeasureText()).
• Redundant values are no longer shown for enum constants, eg. MyEnum.AValue AValue.  Thanks, Martin C.
• Showing a popup for a very long string (like, into the megabytes) no longer hangs Visual Studio for a few seconds – super-long strings are truncated (with an annotation to tell you it’s happened) in the popup.  Thanks, Jools.
• Popups for long strings no longer fall off the bottom of the screen, and popups remember their positions properly in High DPI mode.  Thanks, Martin.

This new release is available from the download page or the gallery.

I’m excited to announce Entrian Inline Watch 1.0 RC:

• You can now specify an alternative object display format for popup windows, which can contain newlines (using \n).  This goes in an optional third column in the Object Display rules, and lets you do this sort of thing:

  

• You can now use a conditional operator with string values in an object display format, eg. Overdrawn: {balance < 0 ? "Yes" : "No"} (thanks, Martin).
• Referencing a non-existent member in an accessor display rule no longer causes a crash (thanks, Martin).
• Popups are now high contrast in high contrast mode.

This is the first non-Beta release of Entrian Inline Watch, meaning that the “Free during Beta”period has ended.  You now get a free trial period of 30 individual days of usage, then you need to buy a license for $29 (or $24 with volume discount).

Should you feel the need to rush off and buy a license right now, the Entrian Inline Watch Online Store is open for business.  🙂

You can download 1.0 RC from the download page or the gallery.

• Hovering over a displayed value now displays a popup showing more information:
  
  For integers, it shows the value in decimal, hex, octal(*) and binary.  For other types (including strings) it shows the full non-truncated value. You can pin those popups, so that they reappear when you re-enter their scope. They’re not constrained to the Visual Studio window, so you can pin them wherever you like, including on a different monitor. 

  (*) Because you’re debugging a PDP-8 using Nixie tubes, right?

• Both object formatting rules and accessor function rules now look up further formatting rules for the members they’re rendering, so if you have a rule for member m_x of type X, and a rule for type X, m_x will be formatted according to the rule for type X.  Thanks, Martin.
• You can now refer to the object itself in a format rule, by using an underscore. For example, to display HWNDs as plain hex, you can create a rule to display HWND__ as {(void*)&_}.  Thanks, Martin.

This new release is available from the download page or the gallery.

(Update: 0.9.13 fixes a bug in the Pinned Popups feature, which now might actually work. 🙂 )

• You can now globally control the displayed decimal places of floats and doubles:
• In your Object Display rules, you can now individually control the displayed decimal places of floats and doubles, selectively overriding the global setting.  For example, ({x,.2f}, {y,.2f}) will round to two decimal places:  (1.23, 4.56) Thanks, Radek and Chris.

As always, this new release is available from the download page or the gallery.

• Accessor Method rules are now as powerful as Object Display rules, eg. Rect->Width() can be defined as {right-left} and display the calculated value (thanks, Martin).
• Increased the default size limit of values, from 15 to 20 characters.
• More compact default representation of single-value objects: {m_SomeMember=”Some string”} truncates to {“Some string”} rather than {m_SomeMe…string”}
• Fixed an intermittent startup crash when the beta expiry date had passed.

As always, this new release is available from the download page or the gallery.

Update: 0.9.6 fixes a bug whereby the crash dialog could crash.  (Did I really just admit to that?)

I’m very pleased to announce Entrian Inline Watch 0.9.3, which introduces two new features:

• You can now set Object Display rules for C++ template types, for instance for std::list you can set up a rule like this:

  std::list   \{size={_Mysize}\}

  to display the size of all std::list<whatever> objects like this: {size=10} (Thanks, Martin and Daniel)

• The display of values for raw pointers in C/C++ is now optional – when there’s no Object Display rule configured for a type, and no sensible default value to display, you can choose whether to display the raw pointer value or nothing (thanks, Daniel).

Update: 0.9.4 adds C++ template support to Accessor Method rules as well as Object Display rules.

You can download the new release from the download page or the gallery.

(If you’re new to Entrian Inline Watch, check out the intro page!)

I’m pleased to announce Entrian Inline Watch 0.9.1, which fixes the following bugs:

• Parameter values are now displayed properly for functions with a throw() signature (thanks, Martin).
• Where there’s no Object Display rule for a class, and the debugger’s default value looks like {ClassName}, don’t clutter the code with it (thanks, Jan and Martin).
• Commenting out a line in the Object Display settings no longer affects the layout of the columns.

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

(Update: version 0.9.2 also updates the Beta expiry date. 🙂 )