Changes between Version 10 and Version 11 of CoordinatedGraphicsSystem

Timestamp:

Aug 3, 2012 1:54:09 PM (12 years ago)

Author:

kenneth@webkit.org

Comment:

--

CoordinatedGraphicsSystem

@@ -202 +202 @@
 == Comments ==
 
-Would be great with more infomation about how vsync and triple buffering fits into all of this (http://hardforum.com/showthread.php?t=928593)
+Q: Would be great with more infomation about how vsync and triple buffering fits into all of this (http://hardforum.com/showthread.php?t=928593)
 
 NR: Vsync/triple-buffering is done in the driver/QtScenegraph level. Added a comment.
 
-It is not so clear how TextureMapper and TextureMapperLayer etc fits together. Like it sounds as TextureMapper is a scene-graph and also a drawing context. Maybe this could be a bit more clear.
+FOLLOW-UP: How does that work in practice? When the driver vsyncs we draw (or swap buffers => blit) on each sync. If we are not ready (no new back-buffer), we will paint the old front-buffer and ending up with a frame rate of vsync/N, where N is some positive number. Triple buffering fixes this. But if we are just a node in the QtSceneGraph which draws (swap => blit) on vsync, I don't see how we become triple buffered.
+
+Q: It is not so clear how TextureMapper and TextureMapperLayer etc fits together. Like it sounds as TextureMapper is a scene-graph and also a drawing context. Maybe this could be a bit more clear.
 
 NR: TextureMapper is a drawing context, TextureMapperLayer is a scenegraph. Updated.
 
-Can UpdateAtlas be used with canvas like in http://dev.dorothybrowser.com/?p=163 ?
+Q: Can UpdateAtlas be used with canvas like in http://dev.dorothybrowser.com/?p=163 ?
 
 NR: yes, we can use a texture atlas for accelerated 2D canvas. However, accelerated 2D canvas is not yet supported and not discussed in this document :)