12 Mar 2012 5:31 PM #11
@zmagyar sorry I meant autodestroy to false.
But...I am looking at Phil's posting after mine, I am really glad some one in Sencha team looked into it and ran into same problem. I am going to try out Phil's suggestion and post back on this thread. I feel a lot comfortable now.
12 Mar 2012 5:51 PM #12
navigation.view is working fine if you create the child view every time. It was behaving the same way with autoDestroy set to false. I'll go with the best practice suggested by Phil.
In ipad safari: (it works fine in chrome)
Unfortunately, when you re-create a view with button component on it, for some reason, button's tap event does not work.
Alternatively, if I try using autoDestory set to false, button component works fine, but its associated audio component does not.
I feel like I am struck after having spent more than 15 hours.
I'd appreciate if you could take a look and let me know how I can fix this problem. You can access the page at www.focusindia.org/sb5/slokas.html and click the top right image.
From list view click couple of items and try and play the music.
12 Mar 2012 6:25 PM #13
hoo..it worked thank fully.
Phil, Thank you for the pointer that setting autoDestroy to false produces erroneous results in child views.
I went with your suggestions and stuck with it. The reason the button in child view does not respond to tap is that - when you press 'back' button in navigation view - not only does it pop the view , when you recreate it, Listeners need to be explicitly added as well.
Once I added the Listeners, it started to work again.
I wish this was communicated in detail when ST2.0 GA was rolled out last week. This has pretty much cost me the last several days and not to talk about the frustration.
But, Phil I Thank you for taking time to respond and@zmagyar for restarting this thread.
I am ready to move on now.
13 Mar 2012 8:18 AM #14
Thanks for the update. Yep, it makes perfect sense to not keep the instance there as in your fix. However the auto destruction seems to be a weird "feature" here. :-)
13 Mar 2012 9:33 PM #15
7 Apr 2012 11:44 AM #16
It helped me too.
But I cannot understand one thing. Once I changed to new code from
it slowed down the entire process (on chrome and safari both) . It took a long time to open the panel.
Any idea why?
11 Apr 2012 10:28 AM #17
I recently updated the citybars app
it now has
at that line number ... is this what you mean?