[Public WebGL] WebGL2 and no mapBuffer/mapBufferRange

Mark Callow [email protected]
Tue Mar 17 06:47:27 PDT 2015


> On Mar 17, 2015, at 3:48 PM, Florian Bösch <[email protected]> wrote:
> 
> On the whole, I don't see a good usecase for the invalidate_range/buffer bits. If you don't care about the data already in the buffer, there's no reason to indicate with those bits that you don't care, you simply don't draw with it. I'd find it more palatable to drop the INVALIDATE_RANGE/BUFFER flags as a workaround to having to introduce expensive machinery to keep track of invalid ranges, than having to throw out the whole mapBuffer[Range] functionality (I actually haven't seen anybody use INVALIDATE_* in practice).


+1

Regards

    -Mark


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://khronos.org/pipermail/public_webgl_khronos.org/attachments/20150317/594a1879/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://khronos.org/pipermail/public_webgl_khronos.org/attachments/20150317/594a1879/attachment.asc>


More information about the public_webgl mailing list