C / C++ / MFC

johny10151981 wrote:

I have started with raw MFC, the reason is to make myself more clear about the behavior of MFC

switch (iMsg)
{
case WM_COMMAND:
   switch (LOWORD(wParam))  // Might be HIWORD, I'm working from memory
   {
      case ID_MY_COMMAND:

Mark Salsbery wrote:

Is there some child control that you're expecting to send WM_COMMAND notifications to your CInsertEdit?

Mark Salsbery wrote:

Fixed speling

class MainWindow

class A; // <- here make B know that A exists
class B
{
private:
	A *a;
public:
	B(A *ta)
	{
		a=ta;
	}
};
class A
{
	int a;
	B *b;
public:
	A()
	{
		b=new B(this);
	}
 
};

class B;
class A
{
	int a;
	B *b;
public:
	A(); 
};

#include "A.h"
#inlcude "B.h"
A::A()
{
 {
  b=new B(this);
 }
}

class A;
class B
{
private:
	A *a;
public:
	B(A *ta)
};

#include "A.h"
#include "B.h"
B:B()
{
 a=ta;
}

// file IDocumentStateCallback.h
class IDocumentStateCallback { // prefix 'I' indicates this is supposed to be an abstract interface
public:
   virtual void OnDocumentChanged()=0;
   // add other callback functions for different types of state changes if you like)
}

// file MainWnd.h
class MainWnd : public CWnd, IDocumentStateCallback {
private:
   void OnDocumentChanged(); // for the interface; doesn't need to be public
// ...
};

// file MainWnd.cpp
void MainWnd::OnDocumentChanged() {
   ReEditTreeControl();
}

// file InsertEdit.h
class CInsertEdit: public CWnd {
   class IDocumentStateCallback* parent;
   void OnSave();
// ...
};

// file InsertEdit.cpp
#include "IDocumentStateCallback.h"
#include "InsertEdit.h"

void CInsertEdit::Create(CWnd* p, /* ... */) {
   parent = dynamic_cast<IDocumentStateCallback*>(p);
// ...
}
void CInsertEdit::OnSave() {
   p->OnDocumentChanged();
}

Member 8012013 wrote:

I happen to own a version of c++ 6

Member 8012013 wrote:

...but I'm also of the impression that with the whole .Net dependencies of the newer versions...

Member 8012013 wrote:

I think I have figured out through trial and lots of error that when the time has expired a message enters the message queue and the code gets to process it when Windows says so. Initially, I was under the impression that SetTimer was giving me a "code interrupt" kind of service when the time expired.

I set up this WHILE(Time_Out_Flag == FALSE){} kinda thing in one particular scope and waited patiently for the OnTimer process to set the Time_Out_Flag to TRUE to escape from the WHILE loop--An event that ultimately would never happen (Ctl+Alt+Del got me control again).