Click here to Skip to main content
15,921,351 members

Comments by Rick York (Top 200 by date)

Rick York 14-Jun-24 16:43pm View    
I think the reason for his problem is in my "BTW" comment. Every time I use a wait cursor suspension of the message loop isn't a problem because changing the cursor forces it to be redrawn.
Rick York 14-Jun-24 12:44pm View    
This is definitely the way to go however, I don't see MFC in the tags for the question so it might not be an option for this person.
Rick York 5-Jun-24 18:39pm View    
You should mark your question as solved so it does not appear on the unsolved list.
Rick York 23-May-24 12:25pm View    
That is a rather curious design if that is what you have to do. I have written a lot of programs that do rendering both 2D (usually GDI+) and 3D (OpenGL, see my profile) and they are almost always double buffered and I have never had a persistent memory DC. It is always drawn to, written to the device, and then automatically deleted. That means this topic has never come up for me because I always do printing from the device. Why do you need to print from the memory context? Also - the printer and device (nearly) always have different resolutions so why does that make a difference in this case?
Rick York 22-May-24 11:53am View    
Deleted
I think those should not have the trailing backslash. The form for a string literal is :
const char * literal = "some text "
"another line of text "
"and it can keep going "
"with no commas or backslashes "
"and then it ends with a semicolon";