Tree: 6ffa8eac51

apple-crashy-msaa-default-framebuffer

audio-import

catastrophic-cross

chainsaw-surgery

dpi-change-events

euler-xxx

findsdl-include-root

gltestlib-symbol-duplication

gpu-preference

inverted-ranges

ktx1-detection

master

meshdata-cereal-killer

mousecapture

multiwindow

next

sceneconverter

scenedata-optimizations

simd

vectorfields

zerocopy

snapshot-2013-08

snapshot-2013-10

snapshot-2014-01

snapshot-2014-01-compatibility

snapshot-2014-06

snapshot-2014-06-compatibility

snapshot-2015-05

snapshot-2015-05-compatibility

v2013.08

v2013.10

v2014.01

v2014.06

v2015.05

v2018.02

v2018.04

v2018.10

v2019.01

v2019.10

v2020.06

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '6ffa8eac51'

${ noResults }

Commit Graph

2 Commits (6ffa8eac51ff79e3b278f9f891ffaafe4c4007e5)

Author	SHA1	Message	Date
Vladimír Vondruš	6ffa8eac51	Using old framebuffer binding internally if new is not supported.	14 years ago
Vladimír Vondruš	5f84edf73d	Split Framebuffer into default and named framebuffers. ... Default framebuffer is now accessible throught defaultFramebuffer global variable, named framebuffers are handled the same way as before. All operations (clear, setViewport, blit, read) now are member functions so they cannot be mistakenly used when unwanted framebuffer is bound. Further rework (DSA, state tracking...) is on the way.	14 years ago