We're happy to announce that the 2017.2 versions of our WPF, Universal Windows, and Silverlight controls have been released.  These versions include some new controls, new features, and a lot of minor updates and bug fixes.

See all the details on the 2017.2 releases in the various announcement posts:

• WPF Controls announcement, and additional maintenance release announcement
• Universal Windows Controls announcement
• Silverlight Controls announcement

SyntaxEditor

Intra-Line Adornments

Full support for intra-line adornments is now included.  These allow whitespace to be reserved above and/or below view lines, and adornments rendered in that space.

A first new sample shows implementation of a Visual Studio-like Code Lens adornment with info display and hyperlink. 

A second sample shows a Visual Studio-like Peek Definition (embedded editor) display.  This is accomplished using a second SyntaxEditor within an adornment of the outer SyntaxEditor.

Vertical Scrolling

Vertical scrolling logic has been refactored to better handle view lines of various sizes.

Code Outlining

A couple new code outlining commands have been added: apply default outlining expansion and expand all outlining.

.NET Languages Add-on Roslyn Extensions

A new optional assembly is available that has Roslyn extensions for loading IBinaryAssembly instances that can be referenced by a project assembly, instead of using normal .NET reflection.

.NET Languages Add-on IntelliPrompt

IntelliPrompt completion is now available for object creation expression initializer member names.

Docking/MDI (WPF/UWP)

Floating Windows

A new property can be data-bound to your VM to float or restore a docking window.  The default location request event allows for specifying that a docking window should open in a floating dock host.  Docking windows that were closed while floating now support more precise restoration later.  Dragging standalone floating docking windows by their tabs now has a better experience.

Contextual Indicators

The read-only contextual indicator for documents now uses a separate display mechanism from the custom contextual indicators, allowing both to show at the same time.

Editors (WPF/UWP)

AutoCompleteBox

A new AutoCompleteBox control has been added that allows text entry and provides suggestions for auto-completion.

This kind of control is ideal for use in search query and quick launch kinds of scenarios.

DateEditBox

Clicking a date on the popup calendar now closes the popup.

Grids (WPF/UWP)

Drag/Drop

The TreeListBox item adapter has been updated with a method that fires when hovering over an item during a drag, allowing you to determine whether it should be expanded.

New adapter methods have also been added that are called immediately before and after a drag, allowing for custom adornments to be displayed while dragging.

Shared Library (WPF/UWP)

AdvancedTextBlock

A new AdvancedTextBlock control has been added that can show a tooltip when overflowed and can highlight spans of text based on captured text ranges (i.e. filter match results).

The 2017.1 versions of our WPF Controls, Universal Windows Controls, and Silverlight Controls were recently released, with the WPF and UWP controls getting some enormous updates in these versions.

The primary focus of the 2017.1 version in WPF and UWP was to add an improved PropertyGrid control and tree controls (TreeListBox and TreeListView) in our new Grids product, and to update Editors to be more modern/lightweight, and share a codebase between the two platforms.  Another focus was on maximizing the performance of all the controls.  The new PropertyGrid for instance shows a massive speed increase over the older WPF v2016.1 PropertyGrid.

See the entire lengthy detailed update list in these announcement posts:

• WPF Controls
• Universal Windows Controls
• Silverlight Controls

If you want to discuss the new controls added in 2017.1 or have suggestions for additional features, please join our #UIControls channel in our Slack team.  It's free and you can chat with us and other customers.

Please note that the v2017.1 WPF Controls have PropertyGrid, Editors, and licensing breaking changes to support better API design and features, so be sure to read the "Converting to 2017.1" topic in the documentation that comes with the controls.  It walks through everything in detail.

Grids is a new product added to the WPF and Universal Windows Controls in v2017.1.  It features three primary controls:  TreeListBox, TreeListView, and PropertyGrid.

TreeListBox

TreeListBox is a single-column control that renders a tree structure.  It is designed to mimic the features found in the Visual Studio Solution Explorer.  You have full control over the appearance of each node, and can easily wire up any tree data model for rendering via the use of our adapter pattern.

The UI tree is virtualized for optimal performance.  Unlike the standard WPF TreeView, TreeListBox is a single ItemsControl that is far less resource intensive and doesn't experience odd vertical scroll jumpiness.

You have full control over whether nodes are expandable, when they load children (and with optional use of async loading with a busy indicator as seen above), and selection modes (single/multiple).  A powerful filtering mechanism is included that allows you to add type-to-filter support.  F2 can initiate inline editing of node text.  Drag and drop can be enabled and you determine what is dragged/dropped.  This just scratches the surface, and there are many other features included.

TreeListView

The TreeListView control builds on top of the foundation provided by TreeListBox and adds multiple columns with an optional header, similar to a standard WPF ListView.

Columns can be sized using several algorithms, resized/reordered by the end user, or certain columns frozen such that they don't scroll horizontally.  Grid lines can be optionally displayed.

PropertyGrid

The PropertyGrid control is based on TreeListView and renders a grid of all the properties of one or more objects and their values. Properties can be displayed by category, alphabetically, or using a custom sort.

A PropertyGrid control was available in older versions of our WPF Controls, but we rewrote much of the internals for v2017.1 and optimized the object model to focus on maximizing speed and ease of use.  The new PropertyGrid can load large complex objects almost instantly.  It's simpler than ever to customize how properties are edited via the use of property editor DataTemplates.  You have full control over which properties are presented and how.

The 2017.1 version ported the Universal Windows Editors back to WPF so that they now share a codebase.  This decision was made because the newer Editors designs are much more lightweight in terms of UI elements used in each control, and the number of bindings involved.  This improves UI performance when using many Editors controls in grids like PropertyGrid.

You'll still find many great editing features such as the ability to use arrow keys when typing in edit boxes to increment or decrement part values.

Each edit box now has an optional dedicated picker control that is used in the drop-down, like the calculator shown above.  The picker can be easily styled if a custom appearance is needed.

In addition to porting the UWP Editors to WPF, we also added a number of new editor controls.  Editors in both platforms feature specialized edit boxes and pickers for these .NET types:  Brush, Byte (WPF only), Color, CornerRadius, Date, DateTime, Double, Enum, Guid, Int16, Int32, Int32Rect (WPF only), Int64, Point, Rect, Single, Size, Thickness, Time, TimeSpan, and Vector (WPF only).

Editors also has these other various miscellaneous controls:  Calculator, CountryComboBox, CurrencyComboBox, EnumListBox, GradientStopSlider, HsbColorPicker, MonthCalendar, RadialHuePicker, Rating, SaturationBrightnessPicker, and Spinner.

The licensing mechanism was updated for the WPF Controls in v2017.1 to be simpler.  Regardless of which WPF products you've licensed from us, your apps will only need a single line in the licenses.licx file going forward.  Please read the Converting to 2017.1 topic in the documentation for details on these updates.

Enjoy the new version!

Hey everyone, we've been working very diligently on the 2017.1 version of our WPF controls for the past several months and a public beta is almost ready.  We'd love as many customers as possible to participate in the beta.  First, let's give an overview of what's new in the 2017.1 version.

Editors Reimagined

In the 2017.1 version, we reimplemented all Editors controls to be faster and more lightweight in terms of elements/bindings, and to use a common codebase with the Universal Windows Editors product.  The new designs are better optimized for use in large quantities such as within data grids or property grids.

Every new edit box control has more fine-grained control over the step values.  Now a native TextBox control is used for input, which allows for more free-form editing, IME input, and better UIA support.

New and improved drop-down pickers have been designed for each edit box.  The pickers are optimized for mouse, pen, and touch-based entry.  The screenshot above shows the BrushEditBox and the new BrushPicker drop-down control.  Altering any edit box's drop-down is simply a matter of providing an alternate Style for its picker control.

New edit boxes have been added for the Byte, Int16, and Single numeric types, along with dedicated date-only (DateEditBox) and time-only (TimeEditBox seen above) variations of DateTimeEditBox.

Tree Controls Added

Our customers have requested custom tree controls from us for a while now and we delivered in this version.  We now offer a new TreeListBox control that is a single column tree similar to a native TreeView but optimized for MVVM usage, virtualization, and speed.  It supports nearly all of the advanced features you'll find in a tree control like the Visual Studio Solution Explorer tree.

We also offer a new TreeListView control that is built upon the TreeListBox control but displays multiple columns similar to a ListView.  Each column supports its own distinct user interface via data templates.

Both of these controls are packaged in a new Grids product.

PropertyGrid Reimagined

While the PropertyGrid control found in our 2016.1 and earlier versions was very feature-rich, its performance sometimes left much to be desired and customization via property editors wasn't very straightforward.

In the 2017.1 version, PropertyGrid has been rewritten from scratch and constructed around the foundation provided by the new TreeListBox and TreeListView controls.  It's now lightning fast and loads complex objects (like the properties of itself) almost instantly.  A lot of this is due to simplification of the internal object model, use of virtualization techniques, and fewer overall UI elements.  You'll definitely notice the speed increase.

The core object model used to track properties and categories has been improved and creating custom property editors is much more straightforward now.

The new PropertyGrid is part of the Grids product as well.

Beta Testers Wanted

If you'd like to help us beta test the product, please write our support address and let us know your existing 2016.1 license information.  We will notify you as soon as the public beta is ready and will send you a 2017.1 license if your subscription is still active. 

The code for the beta is near complete and should be pretty stable.  We have a full array of samples and documentation has been completely updated, including conversion notes.

We also will be chatting about the beta in our Slack channels so please join if you have Slack.

We're pleased to announce that our Universal Windows controls have officially been released and are ready for use in your Windows 10 apps!  Download a free evaluation today and start building your apps with them.

Let's take a quick glimpse at some of the samples that ship with the product and show off the controls:

The focus of this first release was to port our older WinRT XAML controls up to the Universal Windows platform.  Look for plenty more updates and controls added in the future.

The 2015.1 versions of our WPF, Silverlight, and WinRT/XAML controls have been released and are now available for download.

Major new features are described below.  See the announcement posts for the large detailed list of enhancements and updates, including many items not listed below:

• WPF Controls announcement
• Silverlight Controls announcement
• WinRT/XAML Controls announcement

Our Bar Codes product has been ported to the WinRT XAML platform.  This product, which already exists on WPF and Silverlight, allows your apps to render vector-based bar codes using many common 2D and linear bar code symbologies.

A full set of demos and QuickStarts are included to help you get going.

The interop assembly that makes it easy to use Docking/MDI with the Prism framework has been updated to reference the latest Prism v5.0.

We've made numerous layout and performance updates to further improve the product. 

We also have been working hard on building a completely new internal engine for the Docking/MDI product, which will be available sometime later this year.  Keep an eye on our blog for posts detailing the advanced features that are coming with those updates.

All of our edit box controls in the WinRT Editors now have an IsEditable property.  When set to false, the edit box behaves more like a ComboBox, while still retaining the rich popups that make the editors unique.  This is an ideal option for apps whose primary mode of interaction is expected to be touch.

The CornerRadiusEditBox, PointEditBox, RectEditBox, SizeEditBox, and ThicknessEditBox controls have been updated to support text parsing one and/or two number entries where appropriate, which is useful for easy uniform value entry.

In the above ThicknessEditBox, a 2 is typed and then Enter is pressed.  The value is converted to a uniform thickness of 2.

A ValueChanged event has been added to all edit boxes, which fires when a value change is committed.

Finally, edit box padding has been adjusted so that more content is visible in the same amount of space.

A new DigitalGauge.CharacterSegmentThickness property allows for segment thickness adjustments.  This gives you even finer control over the presentation of your digital characters.

We've enhanced the 'Linear Gauge Rolling Scale' QuickStart with a new infinite rolling scale example for navigation headings.

The EditorSearchView control now supports an optional "Find All" button.

The RTF export logic has been updated to support extended ASCII characters.

The free CSS language definition now supports the syntax highlighting of media queries.

We've dramatically improved the speed of large completion list display.

Several other performance improvements have been made, such as optimized the scenarios for which the TokenTagger raises its TagsChanged event, and refining of the automatic outlining update logic.

In the WinRT version, we added the SyntaxEditor.AreSelectionGrippersEnabled property, which determines whether the selection grippers show after touch within a view.

.NET Languages Add-on

The C# parser has been improved to recover better when encountering open block statements so that its AST node structure remains better in tact.

The IntelliPrompt quick info for properties now includes accessors, making it possible to see whether a property is read-only.

Python Language Add-on

The Python language has received an enormous amount of updates, that in sum really improve the entire automated IntelliPrompt feature set.

Check out all these enhancements:

• Added IntelliPrompt for private members and updated the completion list to have Public and All filter tabs.
• Added reflection data for private methods/fields of built-in primitive types.
• Added IntelliPrompt for built-in exception types.
• Improved IntelliPrompt for numerous built-in modules.
• Greatly improved IntelliPrompt for package and module imports.
• Improved IntelliPrompt for function parameters by examining available assert statement isinstance calls.
• Added IntelliPrompt for static fields on classes.
• Improved the resolution of base types for classes.
• Added the optional IResolver.UnknownReturnTypeReferenceCallback callback that can be used to provide return type references for unknown types.
• Updated the resolver to recognize where 'cls()' in a class method can create a new instance of the related class.
• Updated the IntelliPrompt completion list to filter unmatched items.
• Updated the IntelliPrompt docstring display to retain presentation of line feeds.

The Views product has a new TaskBoard control added, available in all three (WPF, Silverlight, and WinRT) platforms.  TaskBoard can be used to create a board of reorderable columns and cards.  All of the drags use smooth animations to give you the feel that you are really interacting with the object.

The first full-source sample that comes with the control is a Repair Shop Scheduling demo, which shows how a TaskBoard can be used to interactively schedule work to resources, such as employees. TaskBoard excels at providing a visual way of representing work/tasks (displayed as cards) within a queue of some sort (displayed as a column).

The second sample is a Task Planning demo, which shows how a TaskBoard can visually organize a project's tasks.

We've added another new primitive SemiEllipse shape, which renders half of an ellipse.

The existing Triangle shape has a new IsClosed property that when set to false will create a triangle with only two of the sides rendered.

Finally, in the WPF Shared Library, we added GradientBrushSlider.CanAddStops and CanRemoveStops properties that determine whether stops can be added and removed from a GradientBrushSlider.