mth/ebiten
1
0
Fork 0
mirror of https://github.com/hajimehoshi/ebiten.git synced 2024-12-25 03:08:54 +01:00
Code Issues Packages Projects Releases Wiki Activity

internal/atlas: rename replacePixels -> writePixels

Browse Source
This commit is contained in:
Hajime Hoshi 2022-09-13 06:39:29 -07:00
parent 243c224003
commit 67ceaf5874
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
internal/atlas/image.go
View File

@ -498,12 +498,12 @@ func (i *Image) drawTriangles(srcs [graphics.ShaderImageCount]*Image, vertices [
func (i *Image) WritePixels(pix []byte, x, y, width, height int) { func (i *Image) WritePixels(pix []byte, x, y, width, height int) {
backendsM.Lock() backendsM.Lock()
defer backendsM.Unlock() defer backendsM.Unlock()
i.replacePixels(pix, x, y, width, height) i.writePixels(pix, x, y, width, height)
} }
func (i *Image) replacePixels(pix []byte, x, y, width, height int) { func (i *Image) writePixels(pix []byte, x, y, width, height int) {
if i.disposed { if i.disposed {
panic("atlas: the image must not be disposed at replacePixels") panic("atlas: the image must not be disposed at writePixels")
} }
if l := 4 * width * height; len(pix) != l { if l := 4 * width * height; len(pix) != l {
@ -544,7 +544,7 @@ func (i *Image) replacePixels(pix []byte, x, y, width, height int) {
// TODO: Is clearing edges explicitly really needed? // TODO: Is clearing edges explicitly really needed?
const paddingSize = 1 const paddingSize = 1
if paddingSize != i.paddingSize() { if paddingSize != i.paddingSize() {
panic(fmt.Sprintf("atlas: replacePixels assumes the padding is always 1 but the actual padding was %d", i.paddingSize())) panic(fmt.Sprintf("atlas: writePixels assumes the padding is always 1 but the actual padding was %d", i.paddingSize()))
} }
rowPixels := 4 * pw rowPixels := 4 * pw
for i := 0; i < rowPixels; i++ { for i := 0; i < rowPixels; i++ {