|
At $50 an hour, after 8 hours, the amout of time you spend trying to track this down would have paid for a copy of Rational Purify.
Now go slap your boss around and get him to buy the package for you.
Tim Smith
I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?
|
|
|
|
|
Try to install and use NU Mega Bounds Checker. Mail me, and I tell you a link for cracked version! 
|
|
|
|
|
Hi,
I want to update a CListBox derived class (adding many lines and deleting some). My problem is the scrollbar becomes mad (updated every time I change listbox items). I want it updated only once, after the full update. But how?
Step 1: I traced messages with MS Spy++. A WM_PAINT cause a repaint of the scrollbar, the WM_PAINT sends a ON_WM_NCPAINT(). I guess it's send directly to the scrollbar, because I do not receive a ON_WM_NCPAINT() in the listbox in that case.
Step 2: Well, maybe I need to handle the WM_PAINT and stop all WM_PAINTs while updating my CListBox (even better). I have a BOOL telling me when I'm updating.
Step 3. The WM_PAINT handler from my CListBox is empty and the default handler CListBox:OnPaint() does nothing. Now I'm stuck....
Thx for any help!
|
|
|
|
|
have you tried LockWindowUpdate/UnlockWindowUpdate ?
-c
Cheap oil. It's worth it!
|
|
|
|
|
Also look at the SetRedraw method (which is just a wrapper for WM_SETREDRAW).
Tim Smith
I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?
|
|
|
|
|
thx Tim, SetRedraw() worked pretty good!
I still have some flickering (especially the border), but I want to add a memory DC later and I guess it's all gone then.
greets, Moak
|
|
|
|
|
Suppose I have a struct of the following type:
struct BBG_SECURITIES {
long nRecords; // Number of Entries
CString *sName; // Security Name
CString *sTicker; // Security Ticker
CString *sMarket; // Security Market
CString *sIssuer; // Issuer
CString *sCoupon; // Coupon
CString *sFrequency; // Frequency
CString *sMaturity; // Maturity Date
CString *sCurrency; // Currency
CString *sCountry; // Country
CString *sDBRS; // DBRS Bond Rating
CString *sSP; // S&P Bond Rating
CString *sMoody; // Moody's Bond Rating
CString *sBloomberg; // Bloomberg Composite Bond Rating
};
As you can see it has a combinantion of heap and stack variables inside. Is it a good practice first of all?
I expect to have no more than 1000 records. When creating a new struct of BBG_SECURITIES type, am I better off declaring it on heap or on stack? I have read somewhere that all structs are extually declared on stack (is this true?). I expect to use the struct created quite often in the program, and I will need speed but I do not want to put a drain on memory (cause I will need a lot of it for something else as well).
Thanks.
|
|
|
|
|
Unless you've got a strong reason not to do it, you'll be much better off declaring your member variables as straight CStrings (i.e. not pointers). Maintaining the integrity of your program when it comes to copying objects can be a real nightmare if you use pointers throughout. Besides, the overhead incurred by copying CString is negligible in most cases (and certainly it is if you don't expect to have more than 100 objects around.)
As for whether to store objects in the heap or in the stack, my advice is: declare everything in the stack unless you cannot (the reasons why you cannot should be obvious when you come to them.)
Another advice. Use extensively BBG_SECURITIES& (or even better const BBG_SECURITIES&) as the parms of your functions whenever it is doable.
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
Hi:
Thanks for your reply.
I am sort of a newbie, and I am not sure what you mean by that, and what it actually does:
>Another advice. Use extensively BBG_SECURITIES& (or even better const >BBG_SECURITIES&) as the parms of your functions whenever it is doable.
Thanks
|
|
|
|
|
OK. Suppose you've got some function like this:
void PrintSecuritiesData(BBG_SECURITIES bbgs); Whenever you call this function, a temporary copy of the BBG_SECURITIES passed is made and pushed onto the stack. If the function happens not to change the object, you can safely replace it with:
void PrintSecuritiesData(const BBG_SECURITIES& bbgs); that does not trigger any copying at all. These are called references, and in may ways act like "hidden pointers". If you've got some C++ tutorial or book check references out to learn more about them.
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
I need to use owner draw methods in a tabctrl.
2 things:
-I don't know how to do it. I've set the TCS_OWNERDRAWFIXED style for it, but where should I now draw it? In the OnDraw method? But how? Does somebody have a sample?
-In fact I want to add some text in the tab itself. That is that I have listcontrols in the tab windows, and I want to show the selected item in the tab. Maybe there is another way to do that.
Please someone help me.
Thanx in advance.
|
|
|
|
|
This article* should be of help
http://www.codeproject.com/tabctrl/lbtab.asp
*Hey Nish, I spelt "article" right!
Roger Allen
Sonork 100.10016
If I had a quote, it would be a very good one.
|
|
|
|
|
Thanx.
What I don't understand is how you get to go through the DrawItem method?
It is a real mistery for me.
|
|
|
|
|
It works now!!
Thanks a lot!!
|
|
|
|
|
First I would like to thank all of you who have made suggestions about this problem you've been a big help. Second I apologize if reposting a topic is considered bad form, but its difficult to find a thread after a couple of days on this forum.
This problem is more bizarre than I had originally thought. As stated before, if the app is run in debug its fine. If the debug .EXE runs outside of debug the app memory usage appears to grow linearly with time. The release .EXE, which I have now built and tested, does the same thing.
Now I've found a new twist...
Following a suggestion from Mike Nordell, I was setting up PerfMon this morning to look at exactly how memory was being used. Unexpectedly while doing this the memory used by the app dropped from 27MB to 17MB. After watching PerfMon for several minutes and wondering about the memory drop I decided to minimize the app then restore it. The memory again dropped. This time to about the original starting value.
If this is a destructor issue how does a minimize/restore change things? Does debug perform some type of clean-up that the OS waits for user interaction to trigger? This isn't Java and I wrote the app to take care of itself, so what gives?
>>>-----> MikeO
|
|
|
|
|
You are looking at the working set size and not the real virtual memory size.
Tim Smith
I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?
|
|
|
|
|
Wasn't sure what you meant at first. 
Went back and looked at the overall memory usage and it is still high. 
So, if it is objects not being released, why does the overall memory usage remain low when debugging remotely?
>>>-----> MikeO
|
|
|
|
|
There is always the chance that due to bugs in your software memory is getting freed in debug build and not in release. The usual cause of this is uninitialized variables in routines. Another cause if writing past the end of allocated memory.
Tim Smith
I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?
|
|
|
|
|
Any known memory issues with maps in the MS STL library?
>>>-----> MikeO
|
|
|
|
|
I think so. Check the updates at Dinkumware. IIRC it's at
http://www.dinkumware.com/vc_fixes.html
Regarding the memory drop when minimizing: As already pointed out it's the working set that drops. The reason for this is that every time you minimize an application, Windows does what in effect is like calling SetProcessWorkingSetSize(GetCurrentProcess(), -1, -1); from within the app itself.
|
|
|
|
|
Easy question, this is.
I want to start a function after a CDialog appears on the screen, after the initialisation and paint functions that is. What message do I use, or which function do I deprecate?
It's a bit like the windowOpened(WindowEvent e) java-equivalent.
I've tried several functions and messages (like WM_SHOWWINDOW), but they all appeared before the dialog showed up.
[VISUAL STUDIO 6.0] [MFC] [WIN98/2]
 Bluute tette!
|
|
|
|
|
Try to handle first occurence of WM_ENTERIDLE message. It should be sent after your dialog had been displayed.
Martin
|
|
|
|
|
How can I change the CDialog message filter to a message filter for Window? Because ENTERIDLE is a Window-message, not a CDialog-message.
[VISUAL STUDIO 6.0] [MFC] [WIN98/2]
Bluute tette!
|
|
|
|
|
Oeps, too hasty. Forgot the clw. Never mind.
[VISUAL STUDIO 6.0] [MFC] [WIN98/2]
Bluute tette!
|
|
|
|
|
I am sorry, I did not realise, WM_ENTRIDLE does not work in CDialog, and you cannot use. Instead of that, you can use WM_KICKIDLE:
1. Include #include <afxpriv.h> to your dialog cpp file.
2. add ON_MESSAGE(WM_KICKIDLE, OnKickIdle) to your message map
3. add function LRESULT OnKickIdle(WPARAM, LPARAM lCount); to your dialog.
It will work in the same way as WM_ENTRIDLE.
Martin
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
