Search Type: Posts; User: brettAV
Search: Search took 0.01 seconds.
24 May 2013 8:09 AM
Sencha CMD 126.96.36.1992 fixed the problem with my Touch 2.1 based application.
When I tried to upgrade the same app to Touch 2.2 it would work fine in the browser but never got passed the app...
17 May 2013 9:13 AM
Until a fix is released uploading a Sencha Touch application packaged with Sencha Cmd to the Apple Appstore is completely broken. We are at their mercy!
Here's the reference of available icons and the letters they map to in ST 2.2.
To get the names they match to look at the bottom of...
10 May 2013 5:05 AM
Is there anyone that's not having this same problem uploading an app packaged with Sencha CMD to the Apple AppStore? Have you tried it in the last few days?
Considering this completely breaks...
Is there anywhere that shows a complete reference of the characters or names that map to the font/icons in the pictos icon set bundled with ST 2.2
There is a list of all the names in the...
8 May 2013 9:15 AM
The same thing is happening to us which means we can no longer upload our app to the App Store. We're using Sencha Cmd 188.8.131.528 and Sencha Touch 2.1.0.
For anyone looking for a workaround you can use the private API for the selectfield to get the picker on a tablet to access the list and deselect everything on painted:
var picker =...
But as far as I can tell this means that there's no way to select the first value and pick up the selection in an event without selecting a different value in the list and then tapping on the...
Ext version tested:
Sencha Touch 2.1
Makes babies cry.
Browser versions tested against:
I got around it by looking at the development.js microloader and more or less manually doing what it does. The key was to add the sencha-touch-all-debug.js script to my index.html. Now I keep an...
I'm having the same problem. PhantomJS/CasperJS works when the app is built with "sencha app build production" but it doesn't work in "development" mode. For some reason in development mode it...
Can anyone explain why we have xtype? I understand that it allows for lazy instantiation but why was this alias implementation chosen over just using the class name. Why do we have:
Results 1 to 12 of 12