Skip to main content

COM Standard Interface

We often create shortcuts for program/documents on Windows desktop. This is a two step process. In step 1 we right click on the desktop and select ‘Create Shortcut’ from the menu that pops up. In step 2 we select the file for which the short is to be created. At times we may want to do this procedure programmatically. Here is the program which, shows how this can be achieved.

When we execute the program a dialog box shown in Figure 1 pops up.


Figure 1.

First we need to select the file for which shortcut needs to be created. This can be done by clicking the ‘browse’ button in the dialog. When we do so the function OnButton1( ) gets called. This function pops up a file dialog and permits the user to select a file. The selected file name and complete path is then retrieved using the functions CFileDialog::GetFileTitle( ) and CFileDialog::Get-PathName( ). The selected file name is then displayed in the edit box of dialog shown in Figure 1.

Now to create a shortcut for this file you need to click the ‘Create Shortcut’ button from the dialog. This leads to a call to OnButton2( ). In this function we have retrieved the data of the name ‘Desktop’ from the registry key HKEY_CURRENT_US-ER\Software\Microsoft\Windows\Current Version\Explorer\Shell Folders’. This has been achieved through calls to API functions RegOpenKeyEx( ) and RegQueryValueEx( ). Next we have built three CString objects namely filename, linkname and descname. If the browsed file has a name ‘c:\about.cpp’ then these CString objects would hold ‘c:\about.cpp’, ‘c:\Windows\desktop\about.lnk’, and ‘shortcut to about’.

Lastly to automatically create the shortcut, the function createshortcut( ) is called. In this function we have created a COM object with CLSID CLSID_ShellLink and an interface ID called IID_ IShellLink. Then using QueryInterface( ) we have enquired whether this component has implemented an IPersistFile interface. If it has then we call the functions SetPath( ) and SetDescription( ) of IShellLink interface and Save( ) of IPersistFile interface. Of these, the SetPath( ) function sets the path and filename of a shell link object, whereas the SetDescription( ) function.sets the description string for a shell link object. The Save( ) function saves the object into the specified file. Lastly the Release( ) function has been called to decrement the reference count of the specified interface.

Comments

Popular posts from this blog

MFC - Microsoft Foundation Classes Design Patterns

1 Introduction This paper describes the use of object-oriented software design patterns, as presented in Design Patterns: Elements of Reusable Object-Oriented Software by Gamma et al., within the Microsoft Foundation Class Library (MFC). MFC is used for implementing applications for Microsoft Windows operating systems. Because of the size of the MFC library, a complete analysis would have been beyond the scope of this assignment. Instead, we identified various possible locations for design patterns, using the class hierachy diagram of MFC, and studied the source carefully at these locations. When we did not find a pattern where we expected one, we have documented it anyway, with examples of how the particular problem could have been solved differently, perhaps more elegantly, using design patterns. We have included a brief introduction to MFC in Section 2 , as background information. The analysis has been split into three parts, with one section for each major design pattern ca...

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 ...

• Why might you need exception handling be used in the constructor when memory allocation is involved?

Your first reaction should be: "Never use memory allocation in the constructor." Create a separate initialization function to do the job. You cannot return from the constructor and this is the reason you may have to use exception handling mechanism to process the memory allocation errors. You should clean up whatever objects and memory allocations you have made prior to throwing the exception, but throwing an exception from constructor may be tricky, because memory has already been allocated and there is no simple way to clean up the memory within the constructor.