Click here to Skip to main content
15,914,408 members

Comments by Rick York (Top 200 by date)

Rick York 3 days ago 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";
Rick York 21-May-24 18:03pm View    
Why in the wide world of sports did this question from August of 2022 need to be updated???
Rick York 15-May-24 3:51am View    
I have written code that does insertion into an array before and I found there two key things. First is pre-allocate more memory than will ever be actually needed for the array. Second is the function memmove is very handy for moving the array elements down to make room for the new item(s). In my case it was an array of characters but the principles are the same.