Printable View
When you resize the window, does Windows invalidate the whole client area? I just wrote a program that writes to the client, and then I resized the window and...BANG...it was nothing. So, I guess I'll have to write an extra code tidbit in WM_PAINT to write it back to the client.
--Garfield
you should be able to make a HDC that is stored in the memory and then re-write it to the main HDC. There is a thread from a while ago that has instructions or search online for help. That should preserve whatever is written. The other choice that I know of is to eliminate the possibility to resize except this annoys people sometimes.
Ummm...couldn't find the thread. Could you explain how to do it or could you link me to the thread? Thanks, I appreciate it.
--Garfield
Create TWO HDC's exactly the same.
Compatible with the HWND from the area you want to draw too and the same size as this area. [GetWindow() for the HWND and GetClientRect() for the size]. If in doubt create them the size of the screen.
One is FrameBufferHDC. This is the HDC to which you will do all the drawing. Create the axis on this one, graph to this one and write text to this one.
When ALL the drawing is finished, call a function that copies the FrameBufferHDC to the ScreenHDC. Do this with BitBlt() or if the screen has changed size, StretchBlt(). [I would get the BitBlt() then go on to the StretchBlt() later]. You will have an area, usually a rectangle that has been redrawn, get this to repaint by calling InvalidateRect(). This will send the WM_PAINT msg.
Call the function [Repaint()] in response to a WM_PAINT msg.
The HDC passed to it should be your ScreenHDC.
As all the drawing is done to one HDC and the repaint from another you can be redrawing the graph AND repainting the screen at the same time.
The paint contains NO calculations and ONE BitBlt() for speed. [BitBlt() is faster and much better than StretchBlt)]
I use a factor, aprox 1.17, to correct the yScale, as the pixcells on the monitor are not square but rectangular. Remember that the Y screen cood go DOWN and the Y scale usually goes UP.
PS make your HINSTANCE a global.
and here is the thread I meant: http://www.cprogramming.com/cboard/s......HELP+PLEASE
Thanks! I'll work on it.
--Garfield
That sounds familar....
What???Quote:
Originally posted by novacain
That sounds familar....
Petzold's book says WM_SIZE is followed immediately by WM_PAINT message. :confused:
yes novacain I copied it out of your exact message to me a few monthes ago (the student has become the teacher :-) )
And...what do you mean?Quote:
Originally posted by golem
Petzold's book says WM_SIZE is followed immediately by WM_PAINT message. :confused:
Nothing, if your program works well.
I'm still not really following you, golem. Oh well.
Basically what golem is saying is that whenever windows sends you a WM_SIZE message it is immediatly followed by a WM_PAINT message. Much the same way that WN_CREATE does. That is why you are losing what your drawing it is automatically repainting when its size changes. Get it?
Yup! Thanks, everyone!Quote:
Get it?
--Garfield