C / C++ / MFC

MFC Extension DLL Problems

29-Apr-02 19:24

I've found it using Hooks.. Smile | :)

MDI aplication

Orbital^28-Apr-02 21:35

Orbital^

28-Apr-02 21:35

Hi!
I'm creting a MDI aplication and I don't want that when I start the aplication a document to be created automaticaly. Any ideas? Confused | :confused:

Bye,
Orbital^

...the night is long ... but not long enought to do some real coding ...

Re: MDI aplication

Orbital^28-Apr-02 22:27

Orbital^

28-Apr-02 22:27

The answer is :

// DON'T display a new MDI child window during startup!!!
cmdInfo.m_nShellCommand = CCommandLineInfo::FileNothing;
Poke tongue | ;-P

Bye,
Orbital^

...the night is long ... but not long enought to do some real coding ...

Re: MDI aplication

Roger Allen28-Apr-02 22:30

Roger Allen

28-Apr-02 22:30

Put this code at the end of you InitInstance for your app

// stop a new document being created if just run normally
if (cmdInfo.m_nShellCommand == CCommandLineInfo::FileNew)
    cmdInfo.m_nShellCommand = CCommandLineInfo::FileNothing ;

Just before the call to ProcessShellCommand

Roger Allen
Sonork 100.10016

If I had a quote, it would be a very good one.

Tony Fontenot28-Apr-02 20:57

Tony Fontenot

28-Apr-02 20:57

I am creating my first MFC Extension DLL. Everything I have read so far said that it would be pretty easy but I have am having some problems.

I want to put a dialog in a DLL so multiple apps can use it. I created the DLL using AppWizard and used ClassWizard to create the CDialog class. I added AFX_EXT_CLASS to export the class. The DLL compiles fine.

Now I go over to the app and try to show the dialog. I enter the lib into the linker's input library list. I add the class' header file to the project, and I include the header in the file. I compile the app and I keep getting this error:

error C2065: 'IDD_FACILITY_CALENDAR_DIALOG' : undeclared identifier

IDD_FACILITY_CALENDAR_DIALOG being the dialog in the DLL

I am also using an OCX in the dialog that exist in the app already, and I am getting a Class redefinition on the wrapper files for the OCX.

Any ideas.
Thanks in advance.

***********************
Tony Fontenot
Recreational Solutions
tony@recsolutions.com
***********************

Re: MFC Extension DLL Problems

Niklas L28-Apr-02 23:35

Niklas L

28-Apr-02 23:35

Your IDD_FACILITY_CALENDAR_DIALOG is defined in your DLL projects Resource.h file. This file is by default not included in your dialogs header, hence the undeclared identifier error. Either include your Resource.h in the dialog header, or remove the enum containing IDD_FACILITY_CALENDAR_DIALOG (IDD) from the header file. It's only used in the constructor. Use IDD_FACILITY_CALENDAR_DIALOG directly in the dialog cpp instead.

As for the OCX I don't know. Does your wrapper contain #ifndefs to protect the header?

Re: MFC Extension DLL Problems

Tony Fontenot29-Apr-02 8:19

Tony Fontenot

29-Apr-02 8:19

I have included the resource.h into the dialog header. The DLL compiles fine. It is when I compile the app that i get the error. As for using the Dlg directly in the cpp, how do go about doing that?

Also I figured out the OCX problem, I just had to add the include statment before another one in the file. Big Grin | :-D

Thanks for yoyr help.

***********************
Tony Fontenot
Recreational Solutions
tony@recsolutions.com
***********************

Re: MFC Extension DLL Problems

Niklas L1-May-02 22:50

Niklas L

1-May-02 22:50

In your header, you have something like: enum { IDD = IDD_CALENDAR_DIALOG };. This is where your problem is. Remove this line.
In your cpp-file, change

CCalendarDlg::CCalendarDlg(CWnd* pParent /*=NULL*/)
	: CDialog(CCalendarDlg::IDD, pParent)

CCalendarDlg::CCalendarDlg(CWnd* pParent /*=NULL*/)
	: CDialog(IDD_CALENDAR_DIALOG, pParent)

and your problems will be gone. Just note that you wont have the class wizards support if you decide to change the ID of your dialog from the resource editor. In this case you will have to change the identifier in the cpp yourself.

COM Problem -

Sameer Maggon28-Apr-02 20:16

28-Apr-02 20:16

Hi,
I have an MFC applciation..
it has one class which uses COM to get history
of the system (internet history)..

But if i install it on some win95 machine that
module is not working.. does the machine require
some runtime environment and how do i deploy that
on that machine..

Christian Graus28-Apr-02 20:35

Christian Graus

28-Apr-02 20:35

Does it use DCOM ? I believe DCOM needs to be installed on a W95 machine.

Christian

The tragedy of cyberspace - that so much can travel so far, and yet mean so little.

And you don't spend much time with the opposite sex working day and night, unless the pizza delivery person happens to be young, cute, single and female. I can assure you, I've consumed more than a programmer's allotment of pizza, and these conditions have never aligned. - Christopher Duncan - 18/04/2002

Sameer Maggon28-Apr-02 20:40

28-Apr-02 20:40

No!.. it does not uses DCOM..

Gaurika Wijeratne28-Apr-02 20:47

Gaurika Wijeratne

28-Apr-02 20:47

you may be missing a file , file can be from IE or windows. first identify it.
you can use Dependancy Walker to see dependancies.

Gaurika Wijeratne. // www.gaurika.com

Boundschecker like product

Max Santos28-Apr-02 23:33

Max Santos

28-Apr-02 23:33

try to see if your code is compatible with the IE ver on the win95

Sameer Maggon28-Apr-02 19:59

28-Apr-02 19:59

Hi,
IS there any other product like
boundschecker which can be integrated
with vc++

Neil Van Note28-Apr-02 20:30

Neil Van Note

28-Apr-02 20:30

Purify

Sameer Maggon28-Apr-02 20:41

28-Apr-02 20:41

Which company? Web site? and can i run it on Windows 98

Neil Van Note28-Apr-02 20:46

Neil Van Note

28-Apr-02 20:46

Sorry, Rational...

I use BoundsChecker myself...

Regards

Sameer Maggon28-Apr-02 20:49

28-Apr-02 20:49

The problem is that i don't own BoundsChecker and neither
can i afford it right now.. so i was looking out for
an evaluation copy.. but i didn't get it newhere

28-Apr-02 23:49

I have BoundsChecker with crack. If you want, mail me ;0)
kourov@newmail.ru

Roger Allen29-Apr-02 0:26

Roger Allen

29-Apr-02 0:26

Boundschecker is a very good product and deserves its price tag.

People who use cracks are only undermining the software industry. You should not be advocating it here or anywhere else.

Roger Allen
Sonork 100.10016

If I had a quote, it would be a very good one.

Mike Nordell29-Apr-02 13:31

Mike Nordell

29-Apr-02 13:31

Boundschecker is a very good product and deserves its price tag.

Perhaps it does nowadays, but rewinding 5-6 years I'd say that Pure Atria Purify kicked ass with whatever was available, and still I use it for memory-related bug-hunting. After Rational bought them (IMO) all went to h*ll though.

I also think that "deserves its price tag" is up to the consumer of it, and if you just want to use it for some personal project it's probably way to expensive.

BoundsChecker still have some merits though:
1 - Old versions can be used to debug Win16 stuff (I've heard of the poor souls forced to do this).
2 - It can keep a "log" of windows (Win32) calls made, and what arguments was given/returned (or have they removed that also in the last years?).

Numega Boundschecker

Sameer Maggon28-Apr-02 19:01