darkfrei wrote: ↑Fri Jun 30, 2023 4:55 am where are you calculates new middleW and middleH after rescaling?

Maybe turn those into getMiddle() function?

Here :o: local lib = {} function lib.load(filename, edgeW, edgeH) local image = love.graphics.newImage(filename) local imageW, imageH = image:getDimensions() local middleW, middleH = imageW - 2*edgeW, imageH - 2*edgeH -- quads: -- 1 2 3 -- 4 5 6 -- 7 8 9 local quad1 = love.graphics.newQuad(0,0, edge...

Looks like I'll have to send the library code again because I couldn't figure everything in your code out to fit mine.

Ok, thanks

darkfrei wrote: ↑Tue Jun 27, 2023 8:47 pm (not tested)

Just tested it, it works the same as the way I tried to write. Of course I've changed something in your code to fit with mine. But still either the quads are broken, they work the different way or we wrote it the wrong way.

What 9patch libraries are there? I know there's patchy and slicy (the fixed version of patchy). But they work different. You need to place pixels in the borders of the image. Are there any other libraries or how to write own with quads? local function newQuadPatch (image, edgeW, edgeH, x, y) local ...

What 9patch libraries are there? I know there's patchy and slicy (the fixed version of patchy). But they work different. You need to place pixels in the borders of the image.

Are there any other libraries or how to write own with quads?

If you know the scaling factor used to scale up the images while drawing, then you just divide the dimensions by the scaling factor, yeah. Of course, that assumes that you know the resulting drawn dimensions of the image. This is because getDimensions returns the dimensions of the texture, it won't...

MrFariator wrote: ↑Mon Jun 26, 2023 5:07 pm If you have an image, you can get its dimensions with getDimensions. Multiply these by your scaling factor.

What about vice versa? Divide these by dimensions?

Or vice versa.