Skip to main content

What Is an ActiveX Control?

ActiveX controls are components that can be used to add new functionality to your application.

ActiveX technologies are all built on top of the COM specification. In COM, an interface is a group of related functions that are implemented together. All interfaces are named beginning with I, such as IDataObject.

An ActiveX control must be a COM object. This means that an ActiveX control must support IUnknown, the interface supported by all COM objects. This allows for a great deal of latitude when deciding how a control is to be implemented;

Support for the IUnknown interface is provided automatically when you use MFC and ControlWizard to build your control.

Reducing the number of required interfaces allows ActiveX controls to be much smaller than the older OLE controls. It also makes it feasible to use ActiveX controls to implement functionality where the size of the control is an important factor. Web pages can be more intelligent when a control is downloaded and activated to your browser. For example, Microsoft's Internet Explorer has support for downloading ActiveX controls from a Web page. Although this opens a lot of exciting functionality, the size of the control to be downloaded must be kept as small as possible.

Interaction with an ActiveX component can be done properties, events, and methods.

  • A property is an attribute associated with the control.

  • An event is a notification message passed to the container by the control.

  • A method is an exposed function that can be applied to the control via IDispatch.

Properties

Properties are exposed by ActiveX controls, as well as by the client where the control is located. There are four basic types of properties:

  • Ambient properties are provided to the control by the container. The control uses these properties in order to "fit in" properly. Commonly used ambient properties include the container's background color, default font, and foreground color.

  • Extended properties are implemented by the container but appear to be generated by the control. For example, the tab order of various controls in a container is an extended property.

  • Stock properties are control properties implemented by the ActiveX control development kit. Examples of stock properties are the control font, the caption text, and the foreground and background colors.

  • Custom properties are control properties that you implement.

Events

An event is used to send a notification message to the control's container. Typically, events are used to notify the container when mouse clicks or other events take place. There are two basic types of events:

  • Stock events are implemented by the ActiveX control development kit and are invoked just like a function call, such as FireError.

  • Custom events are implemented by you, although the MFC class library and ClassWizard handle much of the work for you.

Methods

OLE Automation, now just Automation, is a way of enabling a COM object to be controlled by another party. Automation is provided through the IDispatch interface.

Automation was originally developed so that interpreted languages such as Visual Basic could control COM objects. Now most ActiveX controls use Automation to allow all sorts of programs--even those built using scripting languages such as JScript and VBScript--access to the methods of ActiveX controls.

Labels:

Comments

Post a Comment

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
17 comments
Read more

Explain using static class member ..

A class member declared static is a single instance of that member shared by all instances of this class (that's why it is sometimes termed a class variable, as opposed to object variable). This feature has many uses: for instance, in order to create a file lock, one can use a static bool class member. An object trying to access this file has to check first whether the static (i.e., shared) flag is false. If it is, the object turns the flag on and processes the file safely, since other objects will now find that the flag is now on, and hence -- they cannot access the file. When the object processing the file is done, it has to turn off the flag, enabling another object to access it. How is a static member created? class fileProc { FILE *p; static bool isLocked; //only a declaration; see definition below... public: bool isLocked () const {return isLocked; } }; //somewhere outside the class definition: bool fileProc::isLocked; //definition; initialized to 'false' by defau
9 comments
Read more

the Differences Between static_cast and reinterpret_cast

The operators static_cast and reinterpret_cast are similar: they both convert an object to an object of a different type. However, they aren't interchangeable. Static_cast uses the type information available at compile time to perform the conversion, making the necessary adjustments between the source and target types. Thus, its operation is relatively safe. On the other hand, reinterpret_cast simply reinterprets the bit pattern of a given object without changing its binary representation. To show the difference between the two, let's look at the following example: int n = 9; double d = static_cast < double > (n); In this example, we convert an int to a double. The binary representation of these types is very different. In order to convert the int 9 to a double, static_cast needs to properly pad the additional bytes of d. As expected, the result of the conversion is 9.0. Now let's see how reinterpret_cast behaves in this context: int n = 9; double d = reinterp
2 comments
Read more