|
I used inno setup for a solid 14 months, and I've churned out great installers that are easy to create and yet highly capable. I strongly recommend that you check it out!
"Real men drive manual transmission" - Rajesh.
|
|
|
|
|
I use InstallShield... and its easy to use, but for that price... I'd expect A LOT more (since its freakin' expensive!)...
|
|
|
|
|
Albert Holguin wrote: I use InstallShield... and its easy to use
Wow!  I don't think I've ever heard anyone say that before.
|
|
|
|
|
Really? it is... not much to it... but I hate certain things about it... don't know if they've fixed it since, but in my version, all file links were static!!! why!?!?! so you end up having to put the files in the same EXACT directory structure as they were originally in! very annoying!
|
|
|
|
|
...although i should clarify... it wasn't easy off the back, there was a learning curve, but once you figure it out, its pretty easy to work with and remember
|
|
|
|
|
|
I had to learn it... its what they were using at work  ...but at this point, i can change what i don't like 
...its what i've earned for lack of a life... 
|
|
|
|
|
Hi all,
CFormView::OnClose() ( WM_CLOSE ) event is not coming.
Can u tell me the reason?
|
|
|
|
|
CFormView::OnClose() is not called because views do not have a close button. The close button belongs to the frame window, and OnClose() is a message handler for it.
You could call something in the view from your frame window OnClose(), or add a message handler in the view for WM_DESTROY (OnDestroy()).
|
|
|
|
|
yes thank you.
I have to call OnClose() of View's frame.
|
|
|
|
|
Can any one tell me that how to use visual leak detector.???
I am using visual studio 2003.
Thank u in advance.
|
|
|
|
|
|
Thanx hans
It was very good articles.
But in my Output window I got
No memory leaks detected.
Visual Leak Detector is now exiting.
Detected memory leaks!
Dumping objects ->
{379552} normal block at 0x12F15B10, 102 bytes long.
Data: < C|& * > B8 AE 43 7C 26 00 00 00 2A 00 00 00 01 00 00 00
{379550} normal block at 0x02327DB8, 102 bytes long.
Data: < C| * > B8 AE 43 7C 1F 00 00 00 2A 00 00 00 01 00 00 00
{339020} normal block at 0x02328150, 118 bytes long.
Data: <D : \ Myapp> 44 00 3A 00 5C 00 51 00 50 00 6C 00 75 00 73 00
Object dump complete.
|
|
|
|
|
|
thanx pravin it was nice article
|
|
|
|
|
Helllo everybody
plz help me ... I started one thread in my application in mfc but on close of my view I got memory leak
{367668} normal block at 0x021D82F0, 102 bytes long.
Data: < C|& * > B8 AE 43 7C 26 00 00 00 2A 00 00 00 01 00 00 00
{367666} normal block at 0x121BA1E0, 102 bytes long.
Data: < C| * > B8 AE 43 7C 1F 00 00 00 2A 00 00 00 01 00 00 00
{342539} normal block at 0x02219868, 118 bytes long.
Data: <D : \ MyApp > 44 00 3A 00 5C 00 51 00 50 00 6C 00 75 00 73 00
{254649} normal block at 0x1216AA18, 70 bytes long.
Data: < C| > B8 AE 43 7C 1A 00 00 00 1A 00 00 00 01 00 00 00
{188285} normal block at 0x02259E90, 70 bytes long.
Data: < C| > B8 AE 43 7C 1A 00 00 00 1A 00 00 00 01 00 00 00
Object dump complete.
This errors got. please help me
In on close methode
SetEvent(m_hKillThread);
::TerminateThread (m_Thread->m_hThread,1);
WaitForSingleObject (m_Thread->m_hThread,INFINITE);
m_Thread->Delete ();
CloseHandle (m_hKillThread);
Plz help me
|
|
|
|
|
shashankacharya wrote: ::TerminateThread (m_Thread->m_hThread,1);
Never use TerminateThread, this is a very bad approach. I suggest you read this article[^] from which you will learn a lot for threads. This is a long article but it's definitively worth reading it.
|
|
|
|
|
Thanx Cedric
Before using terminatethread, I used same logic which given into link but at that time I got run time exception on delete Cwin thread..
is there having another way to remove memory leak....
Can vld find out memory leak which occures due to thread termination.
Thank You For your reply...
|
|
|
|
|
First, do not use TerminateThread() to forcely terminate thread. The best way is let the thread terminate itself. If you want to terminate thread while thread is running, set a flag to notify the thread and let it self-terminate. Read the book "Multithreading Applications in Win32", a good book you need to read before you use multithread.
Second, you need to check your code to see where you dynamic created variable but not delete it upon thread exit. You need to check this yourself, no other people can help you.
|
|
|
|
|
Thanx for your reply... I will read that book.
And in my thread I just used local Variable, mydoc variable and my view variables...
|
|
|
|
|
even if you use local variables you'll end up with memory leaks if the thread is not properly shutdown... good luck! 
|
|
|
|
|
|
Hi,
I am linking my app with a number of static libraries which contain dialog resources etc. Unfortuntately, some of the resource IDs appear to be conflicting. I could reallocate the resource IDs in the static libs to overcome this but is there a better way?
Thanks
Tony
|
|
|
|
|
The only IDs that must be unique are dialog IDDs, string IDSs, and menu IDs. The IDCs can be reused (between dialogs) and it won't matter.
To ensure that the dialog IDDs don't collide, you could switch to string resource names, instead of numeric resource IDs. To do this, simply comment out the IDD define in resource.h, and change the ctor of the dialog to use the string form. Also comment out the enum in the dialog header file.
Ideally, the resource.h file should be organized by dialog, so that each IDC is unique; sometimes this can get away from you. You might want to check into the excellent Resource ID Organiser Add-In for Visual C++ 5.0/6.0/.NET[^] as a way of restoring order to resource.h.
|
|
|
|
|
Hi Hans,
Thanks for the reply - that's a great idea!
Thanks again 
Tony
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
