Full Screen mode in Simulator possible?

[toga]

Hi,

i need screenshots of my app in 1920 x 1080. The problem is that i have no device with such a resolution. My Windows 8 Computer is running at that resolution and in the Corona Simulator i could select a device with 1920 x 1080. So my idea would be to take a screenshot from my pc while the appp is running in the simulator. The bad thing is that i am not able to switch the Simulator to a full screen mode so that i could make a hardcopy of my entire screen without the window menus.

Any idea is very appreciated.

Thanks,

Thomas

[Alan_PlantPot]

I created a screenshot capture function and posted it in another topic:

http://forums.coronalabs.com/topic/35922-screen-capture-simulator-feature/

Using this, you can just press a key on the keyboard which will then take a screenshot of the simulated device and save it in the documents directory at the simulated device’s resolution.  

So if you are viewing as an iPad Retina it will save as 2048*1536, if you want to get a 1920*1080 image then just view the simulator as an Ouya or GameStick.

Hope that helps.

One thing I should point out is that occasionally it will save images that are 1 pixel smaller than you are expecting (e.g. 1920*1079). I think this is due to a rounding error, as a workaround I just edit the image manually afterwards and make it 1 pixel wider.

[jonjonsson]

I recommend to use the same method as above but capture the scene view instead. It outputs non lossy png (in documents directory) and then simulator size does not matter:

[lua]

local screenshotName = tostring(os.time()) … “_” … storyboard.getCurrentSceneName() … “.png”

display.save(storyboard.getScene(storyboard.getCurrentSceneName()).view, screenshotName )

[/lua]

You will probably want to convert it for composer.

[Alan_PlantPot]

If the simulator size would then not matter, what size would that method save as? The reason I used my method was to make it easier to get a particular size screenshot for store submissions. If I save the whole scene view, would it not still save at whatever resolution the simulator is set to, or have I missed something?

You’re right that using tostring(os.time()) is so much easier than using table.concat on the date table, not sure why I did that haha.

[jonjonsson]

It saves it in the resolution of the device you choose in the simulator. I was surprised to see this but its very handy. At least on mac it does this.

[Alan_PlantPot]

Ah ok, my function does the same (also on Mac), I thought maybe you meant something else.  

I seem to recall that I had an issue with calling display.save() and passing the group straight in which is why I captured the screen and then saved it, but perhaps that was something that was fixed in a daily build afterwards.

[toga]

@Alan QuizTix
@jonjonsson

Thanks a lot. Great ideas. That is exactly what i need. And thanks for the very fast response. you saved my day

[jonjonsson]

@Alan\_PlantPot

Ah ok, my function does the same (also on Mac), I thought maybe you meant something else.  

I seem to recall that I had an issue with calling display.save() and passing the group straight in which is why I captured the screen and then saved it, but perhaps that was something that was fixed in a daily build afterwards.

OK nice your thing also seems to capture full res even if simulator is zoomed out. I must have been confusing with other capture method that I was using before and captured jpg in simulator size.

[Alan_PlantPot]

I created a screenshot capture function and posted it in another topic:

http://forums.coronalabs.com/topic/35922-screen-capture-simulator-feature/

Using this, you can just press a key on the keyboard which will then take a screenshot of the simulated device and save it in the documents directory at the simulated device’s resolution.  

So if you are viewing as an iPad Retina it will save as 2048*1536, if you want to get a 1920*1080 image then just view the simulator as an Ouya or GameStick.

Hope that helps.

One thing I should point out is that occasionally it will save images that are 1 pixel smaller than you are expecting (e.g. 1920*1079). I think this is due to a rounding error, as a workaround I just edit the image manually afterwards and make it 1 pixel wider.

[jonjonsson]

I recommend to use the same method as above but capture the scene view instead. It outputs non lossy png (in documents directory) and then simulator size does not matter:

[lua]

local screenshotName = tostring(os.time()) … “_” … storyboard.getCurrentSceneName() … “.png”

display.save(storyboard.getScene(storyboard.getCurrentSceneName()).view, screenshotName )

[/lua]

You will probably want to convert it for composer.

[Alan_PlantPot]

If the simulator size would then not matter, what size would that method save as? The reason I used my method was to make it easier to get a particular size screenshot for store submissions. If I save the whole scene view, would it not still save at whatever resolution the simulator is set to, or have I missed something?

You’re right that using tostring(os.time()) is so much easier than using table.concat on the date table, not sure why I did that haha.

[jonjonsson]

It saves it in the resolution of the device you choose in the simulator. I was surprised to see this but its very handy. At least on mac it does this.

[Alan_PlantPot]

Ah ok, my function does the same (also on Mac), I thought maybe you meant something else.  

I seem to recall that I had an issue with calling display.save() and passing the group straight in which is why I captured the screen and then saved it, but perhaps that was something that was fixed in a daily build afterwards.

[toga]

@Alan QuizTix
@jonjonsson

Thanks a lot. Great ideas. That is exactly what i need. And thanks for the very fast response. you saved my day

[jonjonsson]

@Alan\_PlantPot

Ah ok, my function does the same (also on Mac), I thought maybe you meant something else.  

I seem to recall that I had an issue with calling display.save() and passing the group straight in which is why I captured the screen and then saved it, but perhaps that was something that was fixed in a daily build afterwards.

OK nice your thing also seems to capture full res even if simulator is zoomed out. I must have been confusing with other capture method that I was using before and captured jpg in simulator size.