Double buffering
-
Actually what iam doing now means i created one dialog on that iam drawing a image everything is working fine but its flickering continuously.so now my idea was without dialog i want to save that drawing part in memory so that it can be used for showing the report.
-
Actually what iam doing now means i created one dialog on that iam drawing a image everything is working fine but its flickering continuously.so now my idea was without dialog i want to save that drawing part in memory so that it can be used for showing the report.
-
Actually what iam doing now means i created one dialog on that iam drawing a image everything is working fine but its flickering continuously.so now my idea was without dialog i want to save that drawing part in memory so that it can be used for showing the report.
-
Actually what iam doing now means i created one dialog on that iam drawing a image everything is working fine but its flickering continuously.so now my idea was without dialog i want to save that drawing part in memory so that it can be used for showing the report.
-
Actually what iam doing now means i created one dialog on that iam drawing a image everything is working fine but its flickering continuously.so now my idea was without dialog i want to save that drawing part in memory so that it can be used for showing the report.
Double buffering articles. Double Buffering With GDI+[^] Flicker Free Drawing In MFC[^] http://www.robertelder.ca/doublebuffering/[^
-
Actually what iam doing now means i created one dialog on that iam drawing a image everything is working fine but its flickering continuously.so now my idea was without dialog i want to save that drawing part in memory so that it can be used for showing the report.
When your dialog contains an image, and it is flickering, then you're doing the drawing at the wrong place in your code. You should place your drawing code in the
OnDraw(...)
callback. See http://msdn.microsoft.com/en-us/library/e6htdchf.aspx[^]GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto) Point in case: http://www.infoq.com/news/2014/02/apple_gotofail_lessons[^]