Talk:Double Buffering: Difference between revisions
m (Suggestion for expansion among the lines of example code.) |
(→C/C++ examples: new section) |
||
| Line 6: | Line 6: | ||
A thing in the next to last paragraph in the page, the stuff about 'Invalidated rectangles' got me thinking a little... Isn't that practically the same as keeping track of the maximum and minimum pixel coordinates (x,y) you have modified? Which in turn would mean that you have the coordinates for the rectangle which needs to be updated, and don't have to repaint the rest of the screen? Sounds like something that many might find useful and which wouldn't be too hard to code, so my question is, shall I sit down and write a C code snippet for it? Or maybe someone already has an appropriate snippet? |
A thing in the next to last paragraph in the page, the stuff about 'Invalidated rectangles' got me thinking a little... Isn't that practically the same as keeping track of the maximum and minimum pixel coordinates (x,y) you have modified? Which in turn would mean that you have the coordinates for the rectangle which needs to be updated, and don't have to repaint the rest of the screen? Sounds like something that many might find useful and which wouldn't be too hard to code, so my question is, shall I sit down and write a C code snippet for it? Or maybe someone already has an appropriate snippet? |
||
--[[User:Teodor väänänen|Teodor väänänen]] 16:47, 12 July 2009 (UTC) |
--[[User:Teodor väänänen|Teodor väänänen]] 16:47, 12 July 2009 (UTC) |
||
== C/C++ examples == |
|||
Is there really a need for two almost identical pieces of code just to show off reinterpret_cast and the new-operator? If you're writing an OS in C++, you should be familiar with these two anyway. |
|||
--[[User:Darkinsanity|Darkinsanity]] 19:17, 8 November 2014 (CST) |
|||
Revision as of 01:17, 9 November 2014
Double buffering is not difficult. The theory isn't difficult, the code isn't difficult, and it's amazingly easy to use. I fail to see why this has three blocks. JackScott 23:25, 10 April 2009 (UTC)
- I originally put that rating on it not really because of the difficulty, but more because of the fact that it's not something programmers would implement when they're only just starting out. Anyhow, you can change the difficulty rating to whatever you like, I just put it there because it had to have something. -- Creature 11:39, 11 April 2009 (UTC + 1)
A thing in the next to last paragraph in the page, the stuff about 'Invalidated rectangles' got me thinking a little... Isn't that practically the same as keeping track of the maximum and minimum pixel coordinates (x,y) you have modified? Which in turn would mean that you have the coordinates for the rectangle which needs to be updated, and don't have to repaint the rest of the screen? Sounds like something that many might find useful and which wouldn't be too hard to code, so my question is, shall I sit down and write a C code snippet for it? Or maybe someone already has an appropriate snippet? --Teodor väänänen 16:47, 12 July 2009 (UTC)
C/C++ examples
Is there really a need for two almost identical pieces of code just to show off reinterpret_cast and the new-operator? If you're writing an OS in C++, you should be familiar with these two anyway. --Darkinsanity 19:17, 8 November 2014 (CST)