C / C++ / MFC

Jijo raj wrote:

Since its your worker thread, I hope you've the worker thread handle. Look at the place where the thread is getting created. Then you can terminate it by calling TerminateThread().

Manivannan@congruent wrote:

How to capture and terminate a worker thread..?

char* envVarVal;
envVarVal = getenv("PATH");
AfxMessageBox(envVarVal);

pl_kode wrote:

At present I am hardcoding it like..

char path[]="c:\properties\file.properties"

class A
{
public:
virtual void show(){cout<<"Class A invoked"};
}
class B
{
public:
virtual void show(){cout<<"Class B invoked"};
}
class C: public A, public B
{
}

main()
{
C* ptr = new A;
ptr->show(); // "Class A invoked" will be printed
C* ptr1 = new B;
ptr1->show(); // "Class B invoked" will be printed
}

Muhammad Zeeshan wrote:

A class is inheritting from 2 base classes and both the base classes have a function/method with the same name.

Base1       Base2
  \           /
   \         /
        \       /
     Derived

Muhammad Zeeshan wrote:

From the object of the child class how we can call a function of the one base class.

Derived DerivedObject;
DerivedObject.Base1::CommonFunction();

// If its allocated as pointer.
Derived* pDerivedObject = new Derived;
pDerivedObject->Base1::CommonFunction();

lahom wrote:

if i have any kind of operation in one dialog and the result should appear on another dialog

OnPressButton ()
{
  //do your calculation
  CSecondDialog myDialog;
  myDialog.m_varResult = your_calculation_result;
  int nReturn = myDialog.DoModal ();

}

Greetings.
--------
M.D.V.

If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
“The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson
Rating helpfull answers is nice, but saying thanks can be even nicer.