display.save stretches images in the Y direction on save

Solar2D General Questions/Discussion
#1

I started out using display.save on a display group that was x:10/y:10 and not as wide or tall as the screen. When saving, it would save out the image stretched about 11.5 pixels in the Y, and cut off below the capture area, so that each time the image was brought back in and saved, it would grow 11.5 in the Y and cut off at the bottom until I had a fun-house mirror looking picture.

I then tried the new captureBounds with the same result.

I tried multiples of 4 on the size = same result

I then tried just capturing a display group set to the same size as the screen at the 0,0 origin using display.save = same result.

This happens on the mac sim and on my android tablet using Icecream Sandwich.

[import]uid: 169520 topic_id: 30458 reply_id: 330458[/import]

#2

Build: 846 [import]uid: 169520 topic_id: 30458 reply_id: 122034[/import]

#3

I found the problem tho I’m still trying to wrap my head around how this works. It was caused by my sizing in config.lua. [import]uid: 169520 topic_id: 30458 reply_id: 122088[/import]

#4

FYI. I narrowed it down to the zoomEven. I can’t use zoomEven with any w/h numbers… even 320/480 and expect display.save to not stretch.

I’d say this is a bug. zoomEven causes saved images to be stretched and cut-off based on the bounds.

Switched to tablet numbers with zoomStretch and it’s working fine now. [import]uid: 169520 topic_id: 30458 reply_id: 122151[/import]

#5

zoomEven may cut off objects on some devices and zoomStretch may distort objects on some devices. This is not a bug but the result of trying to scale a 320/480 configuration on a device that is of a different screen ratio.

You can use zoomEven if you use the scale factor and view display parameters to position objects from going off screen. I would suggest using letterBox instead to make sure everything dynamically scales correctly. (If you find items are stretched or cut off with letterBox, than it may be a Corona bug.)

For issues like this, it’s best to post sample code of what you’re doing (including the config.lua) and the devices/skins you’re seeing the problem on. [import]uid: 7559 topic_id: 30458 reply_id: 122584[/import]

#6

Build: 846 [import]uid: 169520 topic_id: 30458 reply_id: 122034[/import]

#7

I found the problem tho I’m still trying to wrap my head around how this works. It was caused by my sizing in config.lua. [import]uid: 169520 topic_id: 30458 reply_id: 122088[/import]

#8

FYI. I narrowed it down to the zoomEven. I can’t use zoomEven with any w/h numbers… even 320/480 and expect display.save to not stretch.

I’d say this is a bug. zoomEven causes saved images to be stretched and cut-off based on the bounds.

Switched to tablet numbers with zoomStretch and it’s working fine now. [import]uid: 169520 topic_id: 30458 reply_id: 122151[/import]

#9

zoomEven may cut off objects on some devices and zoomStretch may distort objects on some devices. This is not a bug but the result of trying to scale a 320/480 configuration on a device that is of a different screen ratio.

You can use zoomEven if you use the scale factor and view display parameters to position objects from going off screen. I would suggest using letterBox instead to make sure everything dynamically scales correctly. (If you find items are stretched or cut off with letterBox, than it may be a Corona bug.)

For issues like this, it’s best to post sample code of what you’re doing (including the config.lua) and the devices/skins you’re seeing the problem on. [import]uid: 7559 topic_id: 30458 reply_id: 122584[/import]