Hey Jonathan,
I just reported bug (case #13441).
I tried pausing physics in between scenes but that didn’t help.
I also forgot to say that i’m destroying (calling removeScene) all previous scenes/pages. [import]uid: 77183 topic_id: 24131 reply_id: 99121[/import]
Is there any word as to when build 778 might be available? [import]uid: 42417 topic_id: 24131 reply_id: 99256[/import]
+1 on RobMiracle’s problem.
I had the same problem in build 777, scene appeared beneath curent scene. I just do a remove all on the scenes and it “works” [import]uid: 100901 topic_id: 24131 reply_id: 99319[/import]
If you’d like i can also make 1 minute clip showing the bug/lag on device.?
Thanks for now!
Nick
*EDIT: finally…after 2 weeks i found out what was causing the lag…it was system.setAccelerometerInterval(). if i go above 50, the lag starts to appear.
Jonathan, you can cancel my bug report (case #13441).
Thanks. [import]uid: 77183 topic_id: 24131 reply_id: 99201[/import]
I don’t like to be a bother but I have a client project that we are now making difficult decisions with re: Corona. Do we launch with a lightly-broken 773 or wait for the 778 build and hope for the best? Are there any updates at all in terms of even a rough estimate for this being fixed? I appreciate all of Ansca’s hard work and just want a rough idea of how we should proceed so I can pass this on to the client. [import]uid: 42417 topic_id: 24131 reply_id: 99579[/import]
Build 781: Still no screen capture
Hi,
In 781 I still have the problem described in my earlier post regarding the assumed automatic screen capture. It worked fine with build 775, since 776 this functionality is broken:
Please have a look at my posting above:
http://developer.anscamobile.com/forum/2012/03/30/storyboard-issues-thread-please-post-any#comment-98200
Could you please tell us if this is a problem that you’ll fix or did you intentionally remove the screen capture functionality?
This is quite important as right now three different projects for clients are depending on this.
Best,
Andreas
[import]uid: 107675 topic_id: 24131 reply_id: 99755[/import]
The screen capture was removed due to it being the cause of delays with scene transitions [import]uid: 84637 topic_id: 24131 reply_id: 99779[/import]
I gave 781 a quick spin and it seems to have fixed the “I didn’t specify a transition” bug and I don’t see any problem with fonts…
I won’t know if it addressed some other issues I was having until I can build for devices and put it on my Kindle Fire until later tonight.
But from my quick look, I wouldn’t describe it as a mess. Wonder if something else is going on? [import]uid: 19626 topic_id: 24131 reply_id: 99796[/import]
Just tried 781. It breaks the fonts (stretched or squeezed), gradients are showing horizontally, instead of vertically, a big X sign, border for rectangles are gone… overall big mess.
UPDATE: Ignore the above. I must have clicked on the wrong file to install. The above problems do not exist in 781. [import]uid: 19297 topic_id: 24131 reply_id: 99785[/import]
781 does still have transition bugs:
Animated transition “slide*” from scene1 to scene2 works.
No transition back to scene1 from scene2 does not work (blank screen, no scene at all).
The above *does* work if the animated transition is a CrossFade or a “from*” transition. I did not test the others.
Animated transition from scene1 to scene2 works.
Animated transition back to scene1 from scene2 works.
No transition from scene1 to scene2 works.
No transition back to scene1 from scene2 works.
[import]uid: 44647 topic_id: 24131 reply_id: 99830[/import]
Playing with 781, the new storyboard.loadScene() is something I really want to use in my project. It’s a little buggy though.
On my title screen, I preload the “game” scene with the new function, but now I’m unable to change to any other scene – no matter what scene I goto, all I see is the game scene.
A workaround is to set the game.view.isVisible = false after I load it but that seems like something Storyboard should be doing for me. [import]uid: 44647 topic_id: 24131 reply_id: 99847[/import]
More changes that will be pushed in with an upcoming build (should be out this week) include:
Renamed “enterBegan” event to “willEnterScene” (for clarity)
Renamed “exitEnded” event to “didExitScene” (for clarity)
Fixed bug with storyboard.loadScene() where loaded scene would interfere (thanks @toby2)
Fixed bug where “destroyScene” would get dispatched on every scene purge, regardless if a view existed or not (it should only be dispatched just prior to removing a scene’s view group, if it exists).
@toby2: With all the changes above, I was not able to reproduce the problem you described where scene2 would not go back to scene1 if no effect is specified. If you’re still having this issue once the build with the above changes gets posted, please submit a bug report with a test case demonstrating the problem.
NOTE: The above changes are still under review, so it may or may not end up in the next daily build. Just monitor the daily build release notes for the word “Storyboard”. [import]uid: 52430 topic_id: 24131 reply_id: 99902[/import]
I built my Yosemite Photo Gallery App for Kindle Fire with 781 and the problems demonstrated in post #8 above are still present which was confirmed previously on generic android as well.
I’m not sure they are storyboard related, but there is certainly something not right. This exact code works well on iOS [import]uid: 19626 topic_id: 24131 reply_id: 99903[/import]
@robmiracle: Do the issues on KF/Android devices happen with the Storyboard sample as well? Or just your app? [import]uid: 52430 topic_id: 24131 reply_id: 99907[/import]
EDIT: Nevermind, seems that instead of throwing an error, Corona now just throws a warning about loading the scene instead. Fix a bug and it shows up again. 
(The message is deceptive, but still my fault) [import]uid: 41884 topic_id: 24131 reply_id: 99917[/import]
Another quick update — the changes I described earlier have been pushed in and should be available in daily build 2012.782. [import]uid: 52430 topic_id: 24131 reply_id: 99941[/import]
I still have issues when trying to go back to a previous screen results into screen moving past the device width by half. It looks like below:
\*\*\*\*\*\*\*\* \*\*\*\*\*\*\*\* \*\*\*\*\*\*\*\*
123456 999999 456
123456 \> 999999 \< 456
123456 999999 456
\*\*\*\*\*\*\*\* \*\*\*\*\*\*\*\* \*\*\*\*\*\*\*\*
[import]uid: 19297 topic_id: 24131 reply_id: 99942[/import]
@ckausik: Do you have off-screen objects? If so, where? What effect are you using?
If you can zip up a small test case that demonstrates your issue and file a bug report, that would be the quickest way to narrow down what’s going on. Also ensure you are using the latest daily build—thanks! [import]uid: 52430 topic_id: 24131 reply_id: 99943[/import]
I just built the storyboard sample and ran it on the KF and it ran fine.
I tried to duplicate my using of a secondary group with the same positioning logic my app is using and while vertical it works fine.
I tried to make it a horizontal app and I’m getting a “can’t read package” type error. I’ve obviously screwed up my build.settings file.
But short answer, the storyboard sample runs fine on the KF.
EDIT: Oh I do have off screen objects. By default the caption and control panels that are displaying incorrectly are off screen until the viewer taps them to move them on screen.
[import]uid: 19626 topic_id: 24131 reply_id: 99946[/import]
@ jonathanbeebe: I do not have any off-screen object which is part of the storyboard. I do have an off-screen group which I use as slide down screen for some setting changes. I’ll remove that and check what happens.
I am using 781. It works fine until 768. This belongs to a huge piece of code. I’ll see if I can simulate it with easily.
UPDATE: I removed the off-screen display group. Still no difference.
I am using slideLeft from scene 1 > scene 2 and then slideRight from scene 2 > 1. If I remove the transitions, I get a blank screen when going back from 2 > 1.
UPDATE 2: It only happens in 781 if the scene 1 was first used in loadScene and then in gotoScene. If I call gotoScene directly, no problem at all. If I remember correctly, in one of the earlier versions, that was not the case. [import]uid: 19297 topic_id: 24131 reply_id: 99944[/import]