All the controls missing in WPF. Over 1 million downloads.

wpfthemexamlcontrols

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: f39523515d

master

pr/451

revert-1170-AvalonDock_fix_null_reference_exception

revert-1187-pr/451

3.5.1

3.6.0

3.7.0

3.8.0

4.0.0

4.0.1

4.0.2

4.1.0

4.2.0

4.3.0

4.4.0

4.5.0

4.5.1

4.6.0

4.6.1

4.7.0

5.0.0

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'f39523515d'

${ noResults }

HTTPS

 ZIP  TAR.GZ

brianlagunas_cp f39523515d PropertyGrid: Deleted custom TypeEditorAttribute for defining editors and instead use the already common EditorAttribute provided my the .NET framework. Editors MUST implement the ITypeEditor interface. So now to declare custom editors you define them as follows: private TimeSpan _timeSpan; [Editor(typeof(MyCustomEditor), typeof(MyCustomEditor))] public TimeSpan TimeSpan { get { return _timeSpan; } set { _timeSpan = value; } } public class MyCustomEditor : ITypeEditor { public FrameworkElement ResolveEditor(PropertyItem propertyItem) { TextBox editor = new TextBox(); Binding binding = new Binding("Value"); //bind to the Value property of the PropertyItem instance binding.Source = propertyItem; binding.Mode = propertyItem.IsWriteable ? BindingMode.TwoWay : BindingMode.OneWay; BindingOperations.SetBinding(editor, TextBox.TextProperty, binding); return editor; } }		15 years ago
ExtendedWPFToolkitSolution	PropertyGrid: Deleted custom TypeEditorAttribute for defining editors and instead use the already common EditorAttribute provided my the .NET framework. Editors MUST implement the ITypeEditor interface. So now to declare custom editors you define them as follows:	15 years ago
ExtendedWPFToolkitSolution_35	merges some changes into 3.5 solution	15 years ago