Skip to main content

Explain modal and modeless dialog box ? what is the difference between modal and modeless dialog box ?

A modal dialog box is popped up over the parent dialog( from which it is envoked) it never allows user to go back to parent (calling) dialog box and work until the popped up dialog box is not exited.
Madal dilog box can be displayed as follows.
Ex. class MyDlg; // Class derived from CDialog.
MyDlg myDlg; // create an object
myDlg.DoModal();


A modaless dialogbox is on user can move back and forth between the poped up dialogbox and the parent (calling dialog)
For creating a modless dialogbox. needs to follow follwing things.

Ex. class MyDlg; // Class derived from CDialog.
MyDlg myDlg; // create object
myDlg.create(uint DialogId); // Call create method by providing the dialog resource id.
provide the message handling and run loop.

Difference between modal an modaless dialog box.
modal doesnt allow user to go back to parent window and work in it untill it is not exited while modeless allows to work in parent window.
Other differnce is of creation and displaying of dialog object.
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

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...
5 comments
Read more