2 Jun 2013 8:25 AM #1
Unanswered: Blackbery Playbook and ST 2.2.1
I recently bought a Playbook (they are on sale everywhere - really cheap!) tried the latest version of ST2.2.1 and it appears the forms don't work.
I tried the navigation view example, forms example and the kitchensink none of the form pages in these applications appear to display.
Wanted to know if anyone has experienced the same issues. This is with the latest Playbook os 2.1 they don't support BB10 on the tablets.
4 Jun 2013 4:28 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
What do you mean when you say "doesn't work"?
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services email@example.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
4 Jun 2013 8:17 AM #3
ST2.2.1 - Forms pages appear as blank on the Blackberry Playbook
The Kitchensink form demo page and the Navigation View examples - that display forms pages - appear as blank screens on the Blackberry Playbook - latest OS version (I believe is 2.1.xxxx). This OS is the latest for the tablets - it was updated automatically as soon as the Blackberry was started for the first time.
It appears the panel is displaying just the form elements are not being displayed. Title bar is visible.
17 Jun 2013 6:52 PM #4
ST2.2.X Not Working Properly on BlackBerry Playbook
Is there any word on this?
We've found that any component that has any scrolling functionality doesn't work on Playbook (i.e. it won't scroll).
Also, anything in any List where we have created a custom ListItemComponent (but not a Simple List) - the no items appear in the List.
I could attach a video if it helps.
12 Aug 2013 2:51 AM #5
Blackbery Playbook and ST 2.2.1
I am also experiencing the same problem with forms and scrolling view. I think this is an issue with Translatable.