EXTENDING PROPERTIES PROBLEM

Question

0.00/5 (No votes)

See more:

I have to extend some properties of TextBox and ComboBox
For ex.
First Class-> extTextBox:Inherits TextBox
Properties-> //FocusBackColorChange
//Is_Numeric_Only
//Is_DropDownList

Second Class-> extComboBox:Inherits ComboBox
Properties //FocusBackColorChange
//Is_Numeric_Only

Third Class-> Common_Properties
Properties FocusBackColorChange
Is_Numeric_Only

Now Two Properties from above are common and similarly I have to extend listbox,optionbutton,checkbox and all will have two properties in common
For Ex.FocusBackColorChange
Tagged_Data_Column_Name
Tagged_Data_Table_Name.....etc 20 properties.
The Problem Is how to Inherit the "Third Class" in "First Class" and "Second Class" as Dot net does not support Multiple Inheritance and If I use Interface I have to give the implementation for All the common properties again and It will be double job

Please,suggest me any solution.

Thanks
Sukhen Dass

Posted 1-Feb-12 19:27pm

sukhen dass

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

_Maxxx_ · Answer 1 · 2012-02-01T19:40:00

I've done the same thing previously, and just bitten the bullet, used an interface, and implemented in each inherited control..

This was necessary somewhat as (for example) I implemented some new properties that deeded different implementation depending on the control.

it also allowed me to mix these controls with others that did not implement the interface - so I could check if they did before trying to access these properties, where I had a generic reference to some control (e.g. I highlighted controls that were in error using a property "IsInError" and my validation block could just test if the control implemented the interface, and set IsInerror if it did/.

If you don't need them to be properties, you could use extension methods and implement Get_Is_Numeric_Only and Set_Is_Numeric_Only

you could (depending on the scope) add each of the controls in question to a user control that implements the common properties, and exposes any others you need - but this can be over complex when different controls are involved.