When you have a property that is bool? or ToggleState, it would be good to have three-state functionality for the PropertyGridCheckBoxItemElement.
RadSpinEditor now supports null values. This functionality is relevant for the PropertyGridSpinEditor as well http://docs.telerik.com/devtools/winforms/editors/spineditor/null-value-support
Until the new feature is officially released please use the implementation in the attached project.
Here is the code that should be used for custom sub-properties private void OnCreateItem(object sender, CreatePropertyGridItemEventArgs e) { e.Item = new MyPropertyGridItem((PropertyGridTableElement)sender, e.Parent); } As visual studio would be happy of you only provide a constructor with one argument when you inherit from PropertyGridItem you have no way of knowing that you need a second one where the parent should be the second argument. The proper way to handle this would be to set the parent internally.
Workaround: class MyRadPropertyGrid : RadPropertyGrid { protected override void WndProc(ref Message m) { switch (m.Msg) { case 0x7b: Point point; int x = Telerik.WinControls.NativeMethods.Util.SignedLOWORD(m.LParam); int y = Telerik.WinControls.NativeMethods.Util.SignedHIWORD(m.LParam); if (((int)((long)m.LParam)) == -1) { point = new Point(this.Width / 2, this.Height / 2); } else { point = this.PointToClient(new Point(x, y)); } this.PropertyGridElement.PropertyTableElement.ProcessContextMenu(point); return; } base.WndProc(ref m); } }
Extend the sorting functionality in order to support custom sort order.
More specifically the behavior when the combobox editor is double clicked it changes its current item to the next one.
Currently users can only specify a UITypeEditor. They should be able to specify which BaseInputEditor to be used for a given property when they edit it: [Editor(typeof(PropertyGridBrowseEditor), typeof(BaseInputEditor)] public string FilePath { get; set; }
Currently when expanding an item in RadPropertyGrid the order of the sub items changes on every start.
The RadPropertyGrid editing mechanism can be improved by adding ValueChanged/ing events similar to those in RadGridView.
RadPropertyGrid should not invalidate the properties when the help bar is resized.
The RadPropertyGrid implementation should be improved in a way that will allow users to override the methods that fire events like: OnEditorRequired, OnEditorInitialized, OnCustomGrouping etc. Resolution: 1. Inherit from PropertyGridTableElement and override the method you want. 2. Inherit from PropertyGridSplitElement and override the CreateTableElement() return your class from 1. 3. Inherit from PropertyGridElement and override the CreateSplitElement() return your class from 2. 4. Inherit from RadPropertyGrid and override the CreatePropertyGridElement() return your class from 3.
When applied to a property the editor for this property should show its text as a password.
When a property has a TypeConverter which method GetStandardValuesExclusive returns false. Users should be able to enter additional values, other than the values returned by the GetStandardValues mehtod.
When setting multiple objects or a mix of objects, some of which implement the INotifyPropertyChanged interface changes in these objects should be reflected in the RadPropertyGrid.
The RadPropertyGrid columns should be able to auto resize according to their cells content.