Indrawati wrote: Is there a more efficient way to do this without copying the pixel values back and forth between the two buffers (something like writing the text directly to pData)? nope. not if you're using the GDI text functions - they require DCs, and DCs require HBITMAPs and HBITMAPs require you to SelectObject them, etc.. if you want to get into 3rd party text-rendering engines, you might be able to avoid it, but that's probably a lot more trouble than it's worth. Software | Cleek

:rose: Cool Bio ... Have been searching for this till now ... Dharani Babu S

ShellExecute Bryce --- To paraphrase Fred Dagg - the views expressed in this post are bloody good ones. -- Publitor, making Pubmed easy. http://www.sohocode.com/publitor Our kids book :The Snot Goblin

Are you calling the base class OnEraseBkgnd() ? Ant. I'm hard, yet soft. I'm coloured, yet clear. I'm fruity and sweet. I'm jelly, what am I? Muse on it further, I shall return! - David Williams (Little Britain)

I agree with the other reply. Use the CSliderCtrl and make it owner draw so it looks nicer :) Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

3. I didn't detect any memory leaks, when my app's performance dropped to 4fps, it is only consuming around 10% of the available memory. Two ideas come to my mind: Could it be a memory fragmentation issue? Do you happen to heavily allocate and free memory for each frame? If so, maybe you can try redesigning your stuff so that memory is reused instead, or something along that direction. Maybe you're running out of GDI resources? HTH Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

MFC doesn't come with a layout manager like Java. However, see this[^] and this[^] CP section for answers. /ravi My new year's resolution: 2048 x 1536 Home | Articles | Freeware | Music ravib@ravib.com

Are you looping from 1 to 30, or from 0 to 29 ? Christian I have drunk the cool-aid and found it wan and bitter. - Chris Maunder

As has been pointed out, running the loop in a separate thread is probably the best solution. If you don't want to use multiple threads, see the section "Responding to user input while performing a long task" in this[^] article. /ravi My new year's resolution: 2048 x 1536 Home | Articles | Freeware | Music ravib@ravib.com

Indrawati wrote: will the compiler replace each occurence of MAX_CLIENT with 1000? Yes and no :). It's not a direct textual substitution like a #define, but when the compiler is optimising code it will substitute the variable reference by its value. Indrawati wrote: Should I declare MAX_CLIENT as static const instead? If your header file is used by multiple source files, then yes, otherwise you'll get a bunch of multiple initialisation errors from the linker. Indrawati wrote: And will the same rule apply if MAX_CLIENT is not an int, but a char array? Yes. If it's a char* though, such as char *message = "Message", then make it fully constant, ie. const char * const message = "Message", otherwise the compiler might not treat it as a true constant. Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

Hi Thank you thank you thank you! Yep it's exactly what I'm looking for. The program's OK now when I modified the OnMyMessage() function.

First off, don't use SendMessage to send messages from a thread to a window, use PostMessage to post them instead. To check if a window is still valid use IsWindow(HWND). [ ](http://www.canucks.com)"You're obviously a superstar." - Christian Graus about me - 12 Feb '03 "Obviously ???  You're definitely a superstar!!!" mYkel - 21 Jun '04 Within you lies the power for good - Use it!

Tim Smith wrote: There is nothing wrong with global constants. As you noted, they are the repacement of #define. 2nd on that! I always prefer static const globals over #defines as they are type-checked and that is solid ground for morally sound C++ coding. ~Nitron. ññòòïðïðB A start

Hi aString is a global constant defined in a separate header file. Actually, I defined it as follows: const char *const aString = "anything"; I *think* it should be no problem. Could you please elaborate on the second potential problem (about instanceofB being linked in), since I'm not very clear about it? Thanks!

hi indrawati, in your case, the important thing is that what do your variables do. if there are required to be common for all the objects of the particular class, ie they share the same values, then u will have to use them as static. if this is the case then there should be no problem in the design

Indrawati wrote: will the application run faster if I were to write a memory manager class This is a great post! In Win32 this would only be true if you think you can improve upon the systems memory manager. By default, the Process heap performs coalescing operations. (Coalescing is the act of combining adjacent free blocks to build a larger block.) Coalescing costs additional cycles but reduces internal fragmentation of heap blocks. From: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dngenlib/html/heap3.asp[^] "No matter where you go, there your are." - Buckaroo Banzai -pete

Any STL implimentation is going to be in the form of code that you include. So it's already in your program, the compiler puts it there. Christian I have drunk the cool-aid and found it wan and bitter. - Chris Maunder