I would like to subclass the Microfour.Strataframe.UI.Windows.Forms.DevEx.TextEdit so I don't have to set all the properties each time to get currency box behavior when I drop one on a form (this form will have > 30 ) I will be using this to bind to character fields as well.



I am still a little uncertain as to how masking works in .NET.



I am trying to add a new component, and set the inherits, then set the properties I want in the properties sheet. I get a warning that fProperties has a the exact property in the base class and should be marked Shadows but I'm out of my depth on exactly how to set this up.



I'd be open to any alternative suggestions as to how to create the textbox that will behave right to left, 2 decimals, show with normal backcolor when disabled or readonly etc. The DevEx.TextEdit ( part of the DevExpress freebie in the XtraEditors ) might be the easiest to adapt for my purposes but if anyone has built something else they'd like to share I'd certainly like to see it.



Assume others have been down this path before so I'll look forward to suggestions.



TIA

Okay, I tried stealing the code from the SF source code for the TextEdit wrapper, discovering it is just a class, not a component, so it may well be that my fProperties problem was mostly because I was using a component so there was a design file.



But now there is the question of how to change defaults for properties in my subclass (the whole purpose of doing the subclass to start with )



While my rip-off of the SF wrapper fine - subclassing directly from the DevEx control just as the framework does - builds fine and works as part of my own UI dll , I have discovered that the property sheet allows you to set properties but they do not persist into the built class. Same with subclassing the MaskedTextbox.



Looks like the properties must be over ridden ( shadowed ? ) in the code itself to get new defaults.



Interesting.



Also guessing I'm going to find the DevEx control is going to work differently from the SF MaskedTextbox, since the devEx control uses a repository which seems to be basically a data dictionary approach.



Surely a whole lot of other folks have already dealt with this??? Suggestions ?

Hi Charles,



I've extended a TextEdit control. I did not like the gray coloring for disabled and readonly controls (difficult to read). Also, I wanted the control to reflect any binding length limits. So here is what I did:







I am pretty sure that I started with an empty component. I have seen that fProperties issue. It's been a while since I designed this control, so I do not remember what I did to work around it.



Have a great day!

Bill