C / C++ / MFC

19-Sep-05 5:34

hi, in order to "Enable3dControlsStatic();" would it be define in project setting as preprocessor definition "_AFXSTATIC" or somewhere else? Thanks!

David Crow19-Sep-05 7:40

19-Sep-05 7:40

MFC's AppWizard should have added the call for you automatically. Have you checked the app's InitInstance() method? It typically looks like:

#ifdef _AFXDLL
    Enable3dControls();       // Call this when using MFC in a shared DLL
#else
    Enable3dControlsStatic(); // Call this when linking to MFC statically
#endif

"One must learn from the bite of the fire to leave it alone." - Native American Proverb

Michael Dunn19-Sep-05 16:03

Michael Dunn

19-Sep-05 16:03

Why are you calling that function? The CTL3D functions haven't been relevant since 1995 are are of no use today.

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | 1ClickPicGrabber | NEW~! CP SearchBar v3.0 | C++ Forum FAQ
Strange things are afoot at the U+004B U+20DD

David Crow21-Sep-05 3:36

21-Sep-05 3:36

Michael Dunn wrote:
The CTL3D functions haven't been relevant since 1995 are are of no use today.

How so? I would say the two 3D functions are relevant for all VC++ v6 applications. With MFC v5, I understand it's built in.

"One must learn from the bite of the fire to leave it alone." - Native American Proverb

Michael Dunn22-Sep-05 6:15

Michael Dunn

22-Sep-05 6:15

CTL3D is for giving Windows 3.1 apps a 3-D look. (Only buttons look 3-D in Win3.1) All OSes from 95 on and NT 4 on have the 3-D look natively.

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | 1ClickPicGrabber | NEW~! CP SearchBar v3.0 | C++ Forum FAQ
Magnae clunes mihi placent, nec possum de hac re mentiri.

David Crow22-Sep-05 6:59

22-Sep-05 6:59

I do remember when we had to explicitly load Ctl3d.dll and Ctl3dv2.dll. It was amazing what a little 3D did to an application!

So why then does MFC's AppWizard give you the choice of 3D or not when the target platform is Win32? To my knowledge, MFC 1.0 is the only version that worked on 16-bit Windows. So it somewhat makes sense to leave the code in CWinApp::Enable3dControlsStatic() alone and let it do its check, but for VC++ v6 to still be concerned with it is what puzzles me.

"One must learn from the bite of the fire to leave it alone." - Native American Proverb

Michael Dunn22-Sep-05 7:10

Michael Dunn

22-Sep-05 7:10

Well, CTL3D32 was used on NT 3.51 (which still had the 3.1 UI) and I guess in 1998 when VC6 came out, people were still writing apps for 3.51.

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | 1ClickPicGrabber | NEW~! CP SearchBar v3.0 | C++ Forum FAQ

Networking

sebastianos19-Sep-05 4:51

sebastianos

19-Sep-05 4:51

A very good site with code in Visual C++ about TCP/IP (icmp, finger, whoIs, scan Ports, MacAddress, ...)

www.ipmanager.com.ar

[Message Deleted]

valerie9919-Sep-05 4:45

Re: The one and only object been double defined

19-Sep-05 4:45

[Message Deleted]

MailtoGops19-Sep-05 4:59

MailtoGops

19-Sep-05 4:59

I don't think it is defined two times. Program used reference value. Check other possiblities..

Why do you want to use like this..

--> CWinApp& theApp = (* (static_cast (AfxGetApp())));

use like this..
CWinApp *pApp = AfxGetApp();
ASSERT(pApp != NULL);

" Action without vision is only passing time,
Vision without action is merely day dreaming,
But vision with action can change the world "

- Words from Nelson Mandela

Thanks & Regards,

Gopalakrishnan

thanks, the Dlg is not getting value

valerie9919-Sep-05 5:28

Re: thanks, the Dlg is not getting value

19-Sep-05 5:28

thanks for your reply, the problem with this app is over here:
BOOL CAddSurchrgApp::InitInstance()
{
#ifdef _AFXDLL
Enable3dControls(); // Call this when using MFC in a shared DLL
#else
Enable3dControlsStatic(); // Call this when linking to MFC statically
#endif

CCommandLineInfo CmdLine;
CmdLine.setParamsUsed("C");
ParseCommandLine( CmdLine );

strcpy( m_szCycle, CmdLine.getCycle() );
if ( !CmdLine.isOkToProcess() ) //help will always make this call false so app will stop.
return FALSE;

try
{
CSurchrgDlg dlg;
m_pMainWnd = &dlg;
dlg.DoModal();
}
when it comes to CSurchrgDlg dlg;
the dlg get value {CSurchrgDlghWnd=0xccccccccc}, then it would crash at "m_pMainWnd = &dlg;" because of the access violation.....not sure when and where between those line dlg should get the proper value, thanks for your time!

David Crow19-Sep-05 7:43

19-Sep-05 7:43

valerie99 wrote:
when it comes to CSurchrgDlg dlg;
the dlg get value {CSurchrgDlghWnd=0xccccccccc},

We would need to see more of the CSurchrgDlg class in order to give you any helpful solution(s). What you have shown here is fine.

"One must learn from the bite of the fire to leave it alone." - Native American Proverb

the more of CSurchrgDlg

valerie9919-Sep-05 10:36

Re: the more of CSurchrgDlg

19-Sep-05 10:36

The dlg info should come from CSurchrgDlg, but when I set breakpoint over CSurchrgDlg, it never stop before it hits the CSurchrgDlg dlg;...so I couldn't figure out where exactly it is from

class CAboutDlg : public CDialog
{
public:
CAboutDlg();

enum { IDD = IDD_ABOUTBOX };
protected:
virtual void DoDataExchange(CDataExchange* pDX); // DDX/DDV support
//}}AFX_VIRTUAL

// Implementation
protected:
DECLARE_MESSAGE_MAP()
};

CAboutDlg::CAboutDlg() : CDialog(CAboutDlg::IDD)
{
}

void CAboutDlg::DoDataExchange(CDataExchange* pDX)
{
CDialog::DoDataExchange(pDX);
}

BEGIN_MESSAGE_MAP(CAboutDlg, CDialog)
END_MESSAGE_MAP()

/////////////////////////////////////////////////////////////////////////////
// CSurchrgDlg dialog
CSurchrgDlg::CSurchrgDlg(CWnd* pParent /*=NULL*/)
: CDialog(CSurchrgDlg::IDD, pParent),
m_theApp (* static_cast<cwinapp*> (AfxGetApp()))
{
//{{AFX_DATA_INIT(CAddSurchrgDlg)
m_client_name = _T("");
m_reference = _T("");
m_status_message = _T("");
m_cycle = _T("");
m_percent_complete = _T("");
m_records_changed = _T("");
//}}AFX_DATA_INIT
// Note that LoadIcon does not require a subsequent DestroyIcon in Win32
m_hIcon = AfxGetApp()->LoadIcon(IDR_MAINFRAME);
m_vecBuffer.reserve (BUFFER_SIZE);
}

void CSurchrgDlg::DoDataExchange(CDataExchange* pDX)
{
CDialog::DoDataExchange(pDX);
//{{AFX_DATA_MAP(CAddSurchrgDlg)
DDX_Text(pDX, IDC_CLIENT, m_client_name);
DDX_Text(pDX, IDC_REFERENCE, m_reference);
DDX_Text(pDX, IDC_STATUSMESSAGE, m_status_message);
DDX_Text(pDX, IDC_CYCLE, m_cycle);
DDX_Text(pDX, IDC_PERCENT_COMPLETE, m_percent_complete);
DDX_Text(pDX, IDC_RECORDS_CHANGED, m_records_changed);
//}}AFX_DATA_MAP
}

BEGIN_MESSAGE_MAP(CSurchrgDlg, CDialog)
//{{AFX_MSG_MAP(CSurchrgDlg)
ON_WM_SYSCOMMAND()
ON_WM_PAINT()
ON_WM_QUERYDRAGICON()
ON_BN_CLICKED(IDC_OK, OnOk)
//}}AFX_MSG_MAP
END_MESSAGE_MAP()

David Crow19-Sep-05 10:42

19-Sep-05 10:42

Is there anything in the OnInitDialog() method?

The only "odd" thing I see is this:

CSurchrgDlg::CSurchrgDlg(CWnd* pParent /*=NULL*/)
: CDialog(CSurchrgDlg::IDD, pParent),
m_theApp (* static_cast (AfxGetApp()))

Try removing the initialization of m_theApp and see what that does.

What is m_vecBuffer?

"One must learn from the bite of the fire to leave it alone." - Native American Proverb

OnInitDialog()

valerie9920-Sep-05 3:53

20-Sep-05 3:53

thanks for you reply, I could remove the m_theApp and the app would still crash on the same spot.
the m_vecBuffer is defined like this :
std::vector<receiverec> m_vecBuffer;
in dlg.cpp const std::vector<receivebin>::size_type BUFFER_SIZE = 10000;
BOOL CSurchrgDlg::OnInitDialog()
{
CDialog::OnInitDialog();

// Add "About..." menu item to system menu.

// IDM_ABOUTBOX must be in the system command range.
ASSERT((IDM_ABOUTBOX & 0xFFF0) == IDM_ABOUTBOX);
ASSERT(IDM_ABOUTBOX < 0xF000);

CMenu* pSysMenu = GetSystemMenu(FALSE);
if (pSysMenu != NULL)
{
CString strAboutMenu;
strAboutMenu.LoadString(IDS_ABOUTBOX);
if (!strAboutMenu.IsEmpty())
{
pSysMenu->AppendMenu(MF_SEPARATOR);
pSysMenu->AppendMenu(MF_STRING, IDM_ABOUTBOX, strAboutMenu);
}
}

// Set the icon for this dialog. The framework does this automatically
// when the application's main window is not a dialog
SetIcon(m_hIcon, TRUE); // Set big icon
SetIcon(m_hIcon, FALSE); // Set small icon

// TODO: Add extra initialization here

CWinApp& theApp = (* (static_cast<cwinapp*> (AfxGetApp())));

m_bCanceled = false;
m_strCycle = "";

//PostMessage( WM_COMMAND, IDC_OK );

m_pThread = AfxBeginThread((AFX_THREADPROC)Run, (LPVOID)this, THREAD_PRIORITY_NORMAL, 0);

return TRUE; // return TRUE unless you set the focus to a control
}

void CSurchrgDlg::OnSysCommand(UINT nID, LPARAM lParam)
{
if ((nID & 0xFFF0) == IDM_ABOUTBOX)
{
CAboutDlg dlgAbout;
dlgAbout.DoModal();
}
else
{
CDialog::OnSysCommand(nID, lParam);
}
}

Re: OnInitDialog()

David Crow20-Sep-05 4:16

It crash when it exits...:(

20-Sep-05 4:16

valerie99 wrote:
m_pThread = AfxBeginThread((AFX_THREADPROC)Run, (LPVOID)this, THREAD_PRIORITY_NORMAL, 0);

Comment this out and see what happens.

Does the application crash when it starts or when it is exits?

"One must learn from the bite of the fire to leave it alone." - Native American Proverb

valerie9920-Sep-05 6:30

Re: It crash when it exits...:(

20-Sep-05 6:30

hi, David

If I comment the m_pThread out it will hang forever and with no message show on the dialog.

this app crash when it exits, but if I run another simular app, the dlg from
BOOL CXXXXXDlg::InitInstance()
{
CXXXXXDlg dlg;
would already have the value like {CXXXXXDlghWnd=0x00e90000}, but this one will have {CSurchrgDlghWnd=0xCCCCCCCC} instead, so I think it's because it didn't initialize right, looks like the dlg info is from CDialog, CWnd, but I couldn't find out where exactly it's calling CDialog and getting the info

David Crow20-Sep-05 6:57

even if the breakpoint set on dlg.DoModal();

20-Sep-05 6:57

valerie99 wrote:
...but this one will have {CSurchrgDlghWnd=0xCCCCCCCC} instead, so I think it's because it didn't initialize right...

With the breakpoint on the CSurchrgDlghWnd dlg; statement, CSurchrgDlghWnd.hWnd will likely have a value of 0xcccccccc. This is fine. With the breakpoint on the dlg.DoModal(); statement, CSurchrgDlghWnd.hWnd will likely have a value of 0x00000000. This is fine.

The problem at this point is that the secondary thread you are creating is still active when the application is exiting. What does this thread do? Does it communicate with the main thread or any UI component?

"One must learn from the bite of the fire to leave it alone." - Native American Proverb

valerie9920-Sep-05 10:56

Re: even if the breakpoint set on dlg.DoModal();

20-Sep-05 10:56

Thanks for following up
if I set breakpoint at dlg.DoModal();
{
CSurchrgDlg dlg;
m_pMainWnd = &dlg;
dlg.DoModal();
}
I will still have &dlg with value 0x0000000, dlg 0x0000000 and m_pMainWnd 0x0000000, that's why I keep thinking it's broken at the beginning

I will look more about the secondary thread. thanks!

-- modified at 18:31 Tuesday 20th September, 2005

David Crow21-Sep-05 3:28

21-Sep-05 3:28

If you don't mind me looking at your code (no proprietary or copyright issues), I would suggest packaging it up into a .zip file and e-mailing it to me and I'll take a look at it. Make sure to include the whole project so that I can just open the .dsw file, compile it, and see the problem.

"One must learn from the bite of the fire to leave it alone." - Native American Proverb

wish I could

valerie9921-Sep-05 5:25