Warped on my Huawei Mercury screen is (854x480)
I really like this feature: the only problem i have with it is that when it creates the new object. I see it flash ontop of my loading screen.
Its would be nice to be able to define a creation group.
display.capture( [parentGroup], displayGroup, [saveToPhotoLibraryFlag] )
Warped Image:
[import]uid: 7177 topic_id: 23813 reply_id: 323813[/import]
I reverted to build .768 using display.save and the capture is working without being warped. So something definitely clanged after build 768. [import]uid: 7177 topic_id: 23813 reply_id: 96077[/import]
Wow… I’ve never seen it do this before. Can you tell me which devices this works correctly on please? Like any specific iOS and Android devices… and the Corona Simulator too (Windows or Mac). Might provide a clue to what might be going wrong. [import]uid: 32256 topic_id: 23813 reply_id: 96767[/import]
Ya its weird.
Works in both Mac and Pc Simulators
Working on my Nexus One. build 2.3.6
Working on the Kindle Fire.
Not Working on the (Huawei Mercury) build :build 2.3.5
the Huawei Mercury has a weird screen (854x480)
More detail on the phone http://www.phonescoop.com/phones/phone.php?p=3358 [import]uid: 7177 topic_id: 23813 reply_id: 96825[/import]
Thanks for the info. I’ll write up a bug report for this issue. [import]uid: 32256 topic_id: 23813 reply_id: 96915[/import]
Do you have a the bug number for this Joshua. I have yet to see anyone else having the same problems with the warping images. [import]uid: 7177 topic_id: 23813 reply_id: 103221[/import]
The bug number is 13237. It’s listed as priority 2 and to be fixed by the next stable Corona SDK release.
Right, you have been the only person to report this issue so far… but it wouldn’t surprise me if this is a device specific issue. I haven’t heard of any other Corona developer using that specific device before. Every once in a while we run into OpenGL driver bugs that only happen on certain devices. Namely the Kindle Fire, Nook Tablet, and some HTCs. We work-around these issues the best we can on our end. This just sounds like another device specific issue that we have to work-around.
We do not have your specific device in our office to test with. So when it comes time to fix this issue on our end, would you mind helping us test it? [import]uid: 32256 topic_id: 23813 reply_id: 103377[/import]
I would be more that happy to help and thanks for the reply.
[import]uid: 7177 topic_id: 23813 reply_id: 103455[/import]
Hi Darkmod,
I just noticed that you flagged this as resolved. Just to double check, the firmware patch for your device fixed this issue?
That would make sense. It sounded like an OpenGL driver bug to begin with. [import]uid: 32256 topic_id: 23813 reply_id: 117578[/import]
I just checked again and looks like it is not fixed. I forgot to un-comment some code: "( even with the new firmware i’m getting the warped images.
[import]uid: 7177 topic_id: 23813 reply_id: 117607[/import]
Okay. So, it’s not fixed. Bummer.
Out of curiosity, how did you resolve this issue? Did you work-around it by using a different API? [import]uid: 32256 topic_id: 23813 reply_id: 117623[/import]
I have a display group with around 20-50 objects nested. I use display.capture() on that one group and use the new Image while removing all the old 20-50 objects. This greatly improves the performance. Right now the only work around for this phone is not too use display.capture() and leave the stage with the original 20-50 objects. [import]uid: 7177 topic_id: 23813 reply_id: 117637[/import]
You’re not changing the capture image’s [lua]width[/lua] and [lua]height[/lua] properties are you?
Because that will definitely have weird and unexpected effects on the resulting image. If you want to resize an image display object’s width and height, then you should be adjusting it via its [lua]scale()[/lua] function instead. [import]uid: 32256 topic_id: 23813 reply_id: 117643[/import]
No i don’t change any properties on the captured image. [import]uid: 7177 topic_id: 23813 reply_id: 117648[/import]
Hmmm… I think the problem is happening because the captured pixel width/height is not a multiple of 4. Try taking a screenshot of the entire screen via [lua]display.captureScreen()[/lua] and see if it is still skewed. Or capture the image whose pixel width and height is a multiple of 4. [import]uid: 32256 topic_id: 23813 reply_id: 117769[/import]
display.captureScreen() produces the same result.
[import]uid: 7177 topic_id: 23813 reply_id: 117787[/import]
another phone that fails using display.capture Motorola Photon 4G MB855
display.captureScreen(false) is working
The displayGroup i am capturing is larger than the screen.
[import]uid: 7177 topic_id: 23813 reply_id: 118101[/import]
I was able to work around a similar issue (I’m not certain it’s the same issue) on another thread: http://forums.coronalabs.com/topic/27148-creating-facebook-app-for-android-quesiton/page-3
I was able to work around a similar issue (I’m not certain it’s the same issue) on another thread: http://forums.coronalabs.com/topic/27148-creating-facebook-app-for-android-quesiton/page-3