C / C++ / MFC

compilation speed vs6 vs. vs.net 2003

2-Dec-03 22:46

Please help us understand!

Do you mean when your application "HAS FOCUS" and you type the os or shell makes a sound?

Best Wishes and Happy Holiday's,
ez_way

Re: keyboard

viliam2-Dec-03 23:25

viliam

2-Dec-03 23:25

Yes, my window has focus and I press some key.
It's for example empty dialog box and
key has no effect for it.
But system play some short sound.

Anyway I cannot find where to switch
this in Windows XP options at least.
(for all programs)

viliam

niklo2-Dec-03 22:28

niklo

2-Dec-03 22:28

I just received a copy of a demo fro vs.net2003 and happily installed it to measure its performance for vc++. As a big surprise vc.net 2003 is quite a bit slower! For a simple bench I used a mandelbrot loop (ie not easily optimized away). I also tested simple empty nested for-loops, these are optimized away in vc6 but not in vc.net 2003.
Is there others who have seen this "speed reduction"? Is this a real problem or something that is in the demo version only?

Antti Keskinen3-Dec-03 2:59

Antti Keskinen

3-Dec-03 2:59

The optimization level of VS .NET 2003 is much higher than in VC++ 6. It takes more time to do that. You can take off the optimizations altogether, and the code will compile & link quickly, but will run more slowly.

Compilation/linking speed, however, shouldn't become a big issue until you move to BIG applications (Millions and millions of lines of code). At that point, you'd consider modularizing the application to make it's development easier, and this step would again reduce the time required to build your app.

So even though it complies/links a bit slower, it should't pose a big problem. If you run on a tight time schedule and can't spare time for the compilations, then write bug-free code in the first place so you don't need to do test builds for your app.

As a comparison, compiling the Quake Engine took about 3 minutes with my VC++ .NET 2003. Not much considering how big the engine is...

-Antti Keskinen

----------------------------------------------
The definition of impossible is strictly dependant
on what we think is possible.

niklo3-Dec-03 3:06

niklo

3-Dec-03 3:06

Sorry I was unclear! The actual compilation went ok, pretty fast and actually produced smaller exe. What is the problem is the actual execution! Executing the release build of my mandelbrot test took ~3 times longer for the vc.net 2003 version. Also when running empty for-loops it didn't seem to optimize away those.
Any clues?

Antti Keskinen3-Dec-03 3:22

Antti Keskinen

3-Dec-03 3:22

The first-time execution of any built program in VS .NET 2003 is always slow. If you open a project, build it, then execute/debug it, it will take ages. The next run is already a whole lot faster.

To test the actual execution speeds, build a EXE with VC++ 6, then with VC++ .NET, and then run both applications from the system shell/Explorer instead of inside the Visual Studio.

This will give you a clear picture of how fast the applications are actually executing. I bet that the VC++ .NET version will run faster from the shell than VC++ 6 version does.

I don't know about the empty for-loops, or the reason why it doesn't optimize those. Perhaps the optimization assumes that nobody is stupid enough to write empty loops ? Smile | :)

-Antti Keskinen

----------------------------------------------
The definition of impossible is strictly dependant
on what we think is possible.

niklo3-Dec-03 3:56

niklo

3-Dec-03 3:56

I really need to learn telling people all facts! Yes, I ran the apps from the shell! The mandelbrot test produced the timing: vc.net 4.196s and vc6.0 1.482s

Still I don't know if this is a real problem or just a demo "feature"!? If it's real it's no good!

The code:

// test1.cpp : Defines the entry point for the console application.
//

#include "stdafx.h"
#include <windows.h>

#define WIDTH 100
#define HEIGHT 100
#define ITER 10000

void mandel()
{
double x,y;
double xstart,xstep,ystart,ystep;
double xend,yend;
double z,zi,newz,newzi;
int i,j,k;

xstart = -2;
xend = 2;
ystart = -2;
yend = 2;

/* these are used for calculating the points corresponding to the pixels */
xstep = (xend-xstart)/WIDTH;
ystep = (yend-ystart)/HEIGHT;

/*the main loop */
x = xstart;
y = ystart;
for (i=0; i<height; i++)
="" {
="" for="" (j="0;" j<width;="" j++)
="" z="0;
" zi="0;
" (k="0;" k<iter;="" k++)
="" *="" z^2="(a+bi)(a+bi)" =="" a^2="" +="" 2abi="" -="" b^2=""
="" newz="(z*z)-(zi*zi)" x;
="" newzi="2*z*zi" y;
="" break
="" if(((z*z)+(zi*zi))=""> 4)
{
// no break here always calculate everything!!!
}
#endif
}
x += xstep;
}
y += ystep;
x = xstart;
}
}

int _tmain(int argc, _TCHAR* argv[])
{
unsigned long t;

t = ::GetTickCount();
mandel();
t = GetTickCount() - t;
printf("%u", t);

return 0;
}

open dialog..

R. Thomas2-Dec-03 21:23

R. Thomas

2-Dec-03 21:23

hi...i have a question..
i am using SDI Doc/View arch.
now i dialog that comes up before anything else appears on the screen..
now if the user presses cancel on this dialog..the open file dialog should apprear...
this open dialog is the same on that MFC already gives uswhen we create the SDI proj using AppWizard..
now how can i make this happen???
somethin like making the File->Open menu click through the codes??so that it will open up the Open File Dialog???
i dont really know what am i supposed to do... Frown | :(

hope you can help...
tks a lot... Smile | :)

Have a Super Blessed Day!
-------------------------
For God has not given us a spirit of fear, but of power and of love and of a sound mind.
2 Timothy 1:7
"For God so loved the world that He gave His only begotten Son, that whoever believes in Him should not perish but have everlasting life."
John 3:16
"Therefore you also be ready, for the Son of Man is coming at an hour you do not expet."
Luke 12:40

BaldwinMartin2-Dec-03 22:48

2-Dec-03 22:48

In the app have you placed your dialog and calls before the call to the sdi mainframe?

Best Wishes and Happy Holiday's,
ez_way

R. Thomas3-Dec-03 5:41

R. Thomas

3-Dec-03 5:41

huh???
i dont get it....

Have a Super Blessed Day!
-------------------------
For God has not given us a spirit of fear, but of power and of love and of a sound mind.
2 Timothy 1:7
"For God so loved the world that He gave His only begotten Son, that whoever believes in Him should not perish but have everlasting life."
John 3:16
"Therefore you also be ready, for the Son of Man is coming at an hour you do not expet."
Luke 12:40

BaldwinMartin3-Dec-03 5:50

3-Dec-03 5:50

What don't you get?
In the App like CMyProjectApp
Did you place the dialog there or in the Frame?

Best Wishes and Happy Holiday's,
ez_way

R. Thomas3-Dec-03 15:50

R. Thomas

3-Dec-03 15:50

HUH????????? Confused | :confused:

what dialog?????
there is no dialog......
the question is can i CALL the dilog that comes up when we click : File->Open from the menu that is already given in SDI app by MFC...
that very same open dialog which is made by MFC AppWiard and put inSDI app's menu...
can i call it from my program WITHOUT actually clicking : File->Open
can i call the menu itself from my program without clicking it??
Confused | :confused:

BaldwinMartin4-Dec-03 1:35

Simple dialo app, memory leak

4-Dec-03 1:35

Sure you can!

First allow me to say it is a good question, I just did not understand what you wanted. Most of the guys on this site are pro's and have been programming for years, so we sort of understand what we are talking about, and use the ART of the language itself to communicate. This can lead to problems.

Now:
If you look at your IDR_MAINFRAME-> FILE OPEN property you will see the resource ID -> ID_FILE_OPEN right?

Just for fun let's go to the toolbar and create a new button
and select the properties for the new button ID_FILE_OPEN
compile the project and run it.
see the new button calls File open right?

So how does it do it is your question and can I make the call directly, right?
Yes you can

In the app under initistance
enter this at the bottom ject before retrun TRUE;

OpenMyFile();

Now in the app create a new member function

void CMyCoolApp::OpenMyFile()

Enter this code inside your new function.
{
OnFileOpen();
}

It should look like this now.
void CMyCoolApp::OpenMyFile()
{
OnFileOpen();
}

There you go!

Best Wishes and Happy Holiday's,
ez_way

I received your private message and here is a response to it!

HUH?????????
what dialog?????
there is no dialog......

>> The file open box is a dialog!

the question is can i CALL the dilog that comes up when we click : File->Open from the menu that is already given in SDI app by MFC...

>> Yes I told you how above!

that very same open dialog which is made by MFC AppWiard and put inSDI app's menu...

>> I understand

can i call it from my program WITHOUT actually clicking : File->Open
can i call the menu itself from my program without clicking it??

>> Yes!

Open Program @ File

Best Friend2-Dec-03 21:22

Best Friend

2-Dec-03 21:22

How I click the button and then it will open the program @ file. Example: Window Explorer, Microsoft Work....

Re: Open Program @ File

RChin2-Dec-03 22:32

RChin

2-Dec-03 22:32

Best Friend wrote:
button

What button? Your button, my button, everyone's button?

Best Friend wrote:
program @ file

What's program @ file? Is this a new computer term I've yet to grasp?

---
Your question is not quite coherent, my Best Friend, but are you by any chance
talking about using the ::ShellExecute() API to launch the windows program associated with the given filename?

If so then your question has been answered. Smile | :)

I Dream of Absolute Zero

J.B.2-Dec-03 21:13

J.B.

2-Dec-03 21:13

Hi guys,
I have just learned how to create a dialog-based application with mutiple child dialogs. So far it works fine, however, in Debug window, I always received memory leak warning upon the app exit :

Detected memory leaks!
Dumping objects ->
childdlg.cpp ........

I am just wondering what could cause this?
Basically, say, I have a parent dialog class, say CMyDlg and a child dialog class called CChildDlg. The child class was included on the top of MyDlg.cpp file

#include <ChildDlg.h>

CChildDlg *vChildDlg;

I embedded the child dialog into parent by putting the following codes in OnInitDialog() of the parent's cpp file, MyDlg.cpp.

vChildDlg = CChildDlg();
vChildDlg->Create(IDD_CHILD_DIALOG, this);
vChildDlg->SetWindowPos(this, 20, 20, 50, 50);
vChildDlg->ShowWindow(SW_SHOW);

That looks pretty straight forward. But why on the app's exit, it causes memory leak? Is there something I need to do perhaps in the parent and child class' destructor?

Thanks

Re: Simple dialo app, memory leak

Anonymous2-Dec-03 21:22

Anonymous

2-Dec-03 21:22

the line
vChildDlg = CChildDlg();
creates an instance of CChildDlg.
You need to delete this instance of vChildDlg when the app exits.

Re: Simple dialo app, memory leak

J.B.2-Dec-03 21:43

J.B.

2-Dec-03 21:43

Thank you guys.

I realise I originally placed "delete vChildDlg" in the parent's destructor, which however, was never called. Because the program exit with exit() associated to the exit button in the child dialog.

Re: Simple dialo app, memory leak

Marek Grzenkowicz2-Dec-03 21:23

Marek Grzenkowicz

2-Dec-03 21:23

Don't you use new without delete?

"Gods die, when their believers are gone." --from Sandman by Neil Gaiman

how to get the message for window show?

zecodela2-Dec-03 20:57

zecodela

2-Dec-03 20:57

hi,
i want to know how to get the message after window has been shown. i have checked out with OnShowWindow, WindowPosChanged ... seems that all can report me the Window is about to be shown. that's not ok... as i want to do sth after the window already being seen by the user.
any help?
thanks,
jim

Re: how to get the message for window show?

BaldwinMartin2-Dec-03 22:50