Okay, I tested this and it works :

I'm attaching a C# project that demonstrates it. 

I noticed your class is defined as partial. Is there some other part to it? What happens if you just translate my code into C# and paste directly into a class.cs ?

I'm going to let Greg or Trent step in on this one. Not sure if this works differently in C#.



Looks pretty solid in VB. The code I posted is the entirety of the code in my dxTextEditC.vb class.



When dropped on a form from the toolbox I see all the properties set by default ( including being bolded ) as if I had manually set them as dropping the SF control on.



Are you subclassing the SF wrapper or the Dx control directly?

I just tried this approach (add a constructor with an initialization method) and the control at design-time does not set the properties according to the specifications within the init method. How are you getting this thing to work? I went back to the drawing board on my control (mostly to try out some new ideas), but have gotten back to the same place that I was earlier in the week...setting these properties in a layout method or attaching them to an event (e.g. OnBindingContextChanged).

(addendum )



Here's the properties I added to get the TextEdit control working just the way I want it for 2 decimal numbers :







BTW - the subclassed control is created from a humble Class, not a component or user control or DevExControl or whatever else might look tempting in the templates



You will probalby need to close all forms you may have open and rebuild both the UI Class library and the project using the control in order to see what you need in the toolbox.

Thanks to Bill and Greg, here's the finished dxTextEdit.vb I was trying to get.



This subclasses the Strataframe DevEx wrapper for the DevExpress TextEdit control which is in the XtraEditors 9.3 now available free from DevExpress. In this case I have set default properties to show the textbox normally when disabled, to treat its display and editing as numeric ( though in my usage I am binding to a character field ) and to right align the numbers, both for display and editing. I will probably further refine this as I learn more about how I want to mask it, but this will demonstrate how to simply take advantage of these controls and subclass variations to save some time setting a lot of properties ( this control is being used 50+ times on a form )



From what Greg said the C# implementation may be different and I will leave that to those better qualified.



Note: I have this control in a UI project of my own subclasses of controls. You need to reference



DevExpress.Data.v9.3

DevExpress.Utils.v9.3

DevExpress.Xtra.Editors.v9.3



in your project.

Heh heh...you betcha! I am opening the source code, as we speak. I'll be making the change for my own extended control. Easy-peasy. Just thinking about that future developer...

There is no reason for us to do it when you guys are making the change right now your self. I really don't mind adding it, but no reason to wait on us. Just open the SF source code to see our logic there and then transpose that over to TextEdit control.

Nope...it is NOT on the TextEdit control. Alas!

The control was the MicroFour.StrataFrame.UI.Windows.Forms.Textbox.



Got myself all worked up for nothing.



SF, do you think you could add that little nugget into the extended TextEdit control?



Thanks,

Bill

Dude.



Just saw it.



AutoAdjustMaxLength property on the SF-extended DevEx TextEdit control.



Testing now.