Skip to main content

Explain Customized control development? What is subclassing ?

When we are putting one control on any dialog, we are handling its messages or events in its parent (classes). We use functionalilty and interface provided by that control only. We cannot add our own fuctionality as per our need while handling messages in parent.
Let us take up a scenario when we want an edit control which should accept only letters, digit and specific symbols.

The default functionality will allow on datatypes and minimum maximum values and range validation using DDV(Dynamic Data validation ).
If you are not using Dynamic Data validation then you can validate the edit control values only when you are clicking/hitting return key at list once in control or parent dialog.

To validate the values entered in edit control at runtime we nee to customize the control. This is also called as subclassing, its similar to API Hooking.

Windows Subclassing- usually when and application runs it seeks for messages for its windows. if any messages comes that is handled in the Windows procedure for that application.
While executing the handler for one particular message one can inject some code at some point. this injected code will be executed and control returns to the actual handle code when the code was injected.

To do the subclassing we need to derive a class from control type (which you want to subclass)class. Add the event handlers where you want to do extra processing. And Call the subclass method for that control.

Ex. for an Edit control.

class MyEdit : public CEdit {

// add handlers
};

Call for subclass.

SubClassDlgItem();

Comments

Popular posts from this blog

Explain Polymorphism and Flavors of Polymorphism...

Polymorphism is the ability of different objects to react in an individual manner to the same message. This notion was imported from natural languages. For example, the verb "to close" means different things when applied to different objects. Closing a door, closing a bank account, or closing a program's window are all different actions; their exact meaning is determined by the object on which the action is performed. Most object-oriented languages implement polymorphism only in the form of virtual functions. But C++ has two more mechanisms of static (meaning: compile-time) polymorphism: Operator overloading. Applying the += operator to integers or string objects, for example, is interpreted by each of these objects in an individual manner. Obviously, the underlying implementation of += differs in every type. Yet, intuitively, we can predict what results are. Templates. A vector of integers, for example, reacts differently from a vector of string objects when it receives ...

Function name mangling for C++ and Java

G++ internals - Mangling Both C++ and Jave provide overloaded function and methods, which are methods with the same types but different parameter lists. Selecting the correct version is done at compile time. Though the overloaded functions have the same name in the source code, they need to be translated into different assembler-level names, since typical assemblers and linkers cannot handle overloading. This process of encoding the parameter types with the method name into a unique name is called name mangling . The inverse process is called demangling . It is convenient that C++ and Java use compatible mangling schemes, since the makes life easier for tools such as gdb, and it eases integration between C++ and Java. Note there is also a standard "Jave Native Interface" (JNI) which implements a different calling convention, and uses a different mangling scheme. The JNI is a rather abstract ABI so Java can call methods written in C or C++; we are concerned he...