Changes between Initial Version and Version 2 of Ticket #1157
- Timestamp:
- Apr 24, 2007, 9:50:53 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1157
- Property Summary Mesa Software Renderer add-on don't support direct mode → Mesa Software Renderer add-on doesn't support direct mode
-
Ticket #1157 – Description
initial v2 1 Now that BGLView:: DirectConnected() pass correctly clipped screen region to the delegated renderer, we should make some use of it in our defacto default/fallback renderer, the fully software one.1 Now that BGLView::!DirectConnected() pass correctly clipped screen region to the delegated renderer, we should make some use of it in our defacto default/fallback renderer, the fully software one. 2 2 3 In single buffer opengl mode, we're supposed to blit/span/clear this screen region directly, while in double buffer we could spawn/awake at SwapBuffers() time a thread drawing (eventually doing dithering at fly) the bitmap buffer into the screen region.3 In single buffer opengl mode, we're supposed to blit/span/clear this screen region directly, while in double buffer we could spawn/awake at !SwapBuffers() time a thread drawing (eventually doing dithering at fly) the bitmap buffer into the screen region.