Not blocking, but how much effort would it be to do the right thing here and remove stride(), write() and read() from the mg::Buffer API and move it to the appropriate NativeBuffer interfaces? These things really only apply to (a currently hypothetical) mg::SoftwareTexture.
Not blocking, but how much effort would it be to do the right thing here and remove stride(), write() and read() from the mg::Buffer API and move it to the appropriate NativeBuffer interfaces? These things really only apply to (a currently hypothetical) mg::SoftwareTex ture.