Hey, I’m having issues in finding a working daily build. Everything between 2460 and 2494 seems to work incorrectly with a space in application name (and no, I’m not going to take the space away). But 2494 and 2496 seem to work incorrectly with our image sheets on newImageRect by returning nil with a call which works in 2460.
So would be great to hear which build you use currently? Something older than 2460?
regards,
Jyrki
Can you describe the image issue in more detail? Perhaps some screen shots?
Hi Rob,
There isn’t much to show. Our image assets are in imagesheets created with TexturePacker. We haven’t touched them, but 2489 introduced a change in which this returns with p as nil:
composer.cmet = require("images.all") composer.cframes = composer.cmet:getSheet().frames composer.csheet = graphics.newImageSheet( imagesDir .. "all.png", composer.cmet:getSheet()) local p = display.newImageRect(group[index], composer.csheet, idx, composer.cframes[idx].width, composer.cframes[idx].height)
So it works as it should still in 2484, but not since 2489. Just noticed it yesterday when tried to work my way trough the issue of having a space in the app name.
I don’t see much in the way of differences. 2489 was the build immediately after 2484. It was a maintenance build and I don’t see anything in the release notes that would indicate a change to the rendering engine.
I ran an app of mine that uses image sheets and it’s behaving as expected. I ran the HorseAnimation sample app which uses imageSheets to drive sprites and it’s behaving as it should.
While I suspect there may have been a regression bug introduced with that build, the engineers are going to need help finding it. They are going to ask for a bug report. This bug report should be a small sample app that demonstrates the problem. It will need a build.settings and a config.lua. It will need any assets needed to run the app. Bundle it up in a .zip file (please don’t use other compression types) and then use the File a bug report link at the top of the page.
We are getting close to a public release and we need to stomp out any regression bugs before we can, so the sooner you can file this the better.
Rob
I know. Believe me, that is not the first image sheet call our (rather complex) app makes. I’m doing this part-time nowadays and just don’t have time to start figuring out how to make a reproducible test case for this. That’s why I didn’t file a bug report, but would rather fallback to some build that would just work. As I said, 2484 works and 2489 doesn’t, but I’m hit by that space in the app name issue.
I appreciate where you are coming from. But engineering won’t look at it without a test case.
Rob
Sure, this is understood, but I won’t do testing for CoronaLabs for free either.
Daily Build 2489 actually contained some significant changes but unfortunately the release notes disappeared:
Core - Display object introspection: added properties “_type”, “_properties”, “_defined”, “_lastChange”
Can you confirm the type of the first parameter to your display.newImageRect() call, is it a Group or something else like a Container?
Also, are there any messages in the Corona Simulator console?
Hi!
It’s a group within a group. Here’s all I get:
2014-11-10 22:15:12.074 Corona Simulator[17361:507] Runtime error
/Users/jyrki/Development/adapkit/monsta-points/monsta-points/src/MonstaPoints/util/widgets.lua:276: attempt to index field ‘p’ (a nil value)
stack traceback:
/Users/jyrki/Development/adapkit/monsta-points/monsta-points/src/MonstaPoints/util/widgets.lua:276: in function ‘setIcon’
/Users/jyrki/Development/adapkit/monsta-points/monsta-points/src/MonstaPoints/util/widgets.lua:328: in function ‘init’
/Users/jyrki/Development/adapkit/monsta-points/monsta-points/src/MonstaPoints/util/widgets.lua:432: in function ‘getOccurrences’
/Users/jyrki/Development/adapkit/monsta-points/monsta-points/src/MonstaPoints/itemsummary.lua:1319: in function ‘insertItem’
/Users/jyrki/Development/adapkit/monsta-points/monsta-points/src/MonstaPoints/itemsummary.lua:1499: in function ‘insertItems’
/Users/jyrki/Development/adapkit/monsta-points/monsta-points/src/MonstaPoints/itemsummary.lua:1534: in function ‘insertItems’
/Users/jyrki/Development/adapkit/monsta-points/monsta-points/src/MonstaPoints/itemsummary.lua:1552: in function ‘createsv’
/Users/jyrki/Development/adapkit/monsta-points/monsta-points/src/MonstaPoints/tasksummary.lua:434: in function ‘createScrollView’
/Users/jyrki/Development/adapkit/monsta-points/monsta-points/src/MonstaPoints/tasksummary.lua:612: in function ‘_listener’
?: in function <?:141>
?: in function <?:221>
2014-11-10 22:15:12.075 Corona Simulator[17361:507] appSusp
I’m not having any luck reproducing this. We haven’t received any other similar reports so do you have any thoughts on something different your code might be doing?
I would suggest running through a couple of the sample apps and making sure it’s not a local problem. Then perhaps build a very simple TexturePacker constructed project and see if it happens to you. As Perry said, when we can’t replicate the problem, we need something that will replicate the problem.
Rob
Thank you!
Can you describe the image issue in more detail? Perhaps some screen shots?
Hi Rob,
There isn’t much to show. Our image assets are in imagesheets created with TexturePacker. We haven’t touched them, but 2489 introduced a change in which this returns with p as nil:
composer.cmet = require("images.all") composer.cframes = composer.cmet:getSheet().frames composer.csheet = graphics.newImageSheet( imagesDir .. "all.png", composer.cmet:getSheet()) local p = display.newImageRect(group[index], composer.csheet, idx, composer.cframes[idx].width, composer.cframes[idx].height)
So it works as it should still in 2484, but not since 2489. Just noticed it yesterday when tried to work my way trough the issue of having a space in the app name.
I don’t see much in the way of differences. 2489 was the build immediately after 2484. It was a maintenance build and I don’t see anything in the release notes that would indicate a change to the rendering engine.
I ran an app of mine that uses image sheets and it’s behaving as expected. I ran the HorseAnimation sample app which uses imageSheets to drive sprites and it’s behaving as it should.
While I suspect there may have been a regression bug introduced with that build, the engineers are going to need help finding it. They are going to ask for a bug report. This bug report should be a small sample app that demonstrates the problem. It will need a build.settings and a config.lua. It will need any assets needed to run the app. Bundle it up in a .zip file (please don’t use other compression types) and then use the File a bug report link at the top of the page.
We are getting close to a public release and we need to stomp out any regression bugs before we can, so the sooner you can file this the better.
Rob
I know. Believe me, that is not the first image sheet call our (rather complex) app makes. I’m doing this part-time nowadays and just don’t have time to start figuring out how to make a reproducible test case for this. That’s why I didn’t file a bug report, but would rather fallback to some build that would just work. As I said, 2484 works and 2489 doesn’t, but I’m hit by that space in the app name issue.
I appreciate where you are coming from. But engineering won’t look at it without a test case.
Rob
Sure, this is understood, but I won’t do testing for CoronaLabs for free either.
Daily Build 2489 actually contained some significant changes but unfortunately the release notes disappeared:
Core - Display object introspection: added properties “_type”, “_properties”, “_defined”, “_lastChange”
Can you confirm the type of the first parameter to your display.newImageRect() call, is it a Group or something else like a Container?
Also, are there any messages in the Corona Simulator console?