-
23 Jan 2013 4:37 PM #1
TypeError: 'undefined' is not an object (evaluating 'h.substring') when loading store
TypeError: 'undefined' is not an object (evaluating 'h.substring') when loading store
REQUIRED INFORMATION
Architect Build tested:- Build: 678
- Touch 2.1.x
- Architect throws an error when using a store with a DataView with a custom DataItem.
- Create a model and store named 'store1' that properly loads data, set autoLoad to true. Right click store and click 'Load Data'
- Create a DataItem with alias 'dataitem' with proper style with a child component that has a proper tpl
- Create a DataView and check useComponents, defaultType to 'dataitem', and store to 'store1'
- Click on different views in the Project Inspector to load and reload the CSS for the DataView
- Loading of the store in Architect with the proper layout of DataItems and CSS in the view
- Window saying that an error occured:Code:
TypeError: 'undefined' is not an object (evaluating 'h.substring') Source Class: qrc:/designer/src/frameworks/touch21/framework/sencha-touch-all.js?0.3837460807990283 Line 18
Screenshot, Project, or Video:- attached Project and picture of error
- project.xda
- Mac OS 10.7.5
-
20 Feb 2013 4:17 PM #2
I'd be very interested in at least a reasonable workaround for this bug.
-
20 Feb 2013 4:45 PM #3
Easiest thing would be to not autoload the store while in Sencha Architect.
-
20 Feb 2013 5:33 PM #4
-
20 Feb 2013 6:58 PM #5
I can confirm that the attached project throws an error even in our latest development build.
In a brief cursory look at this it looks like what's happening is that the default list item dependencies is not being taken into account. Ie we have to create teh defaultType class before trying to load the store (otherwise it won't know what to paint)Aaron Conran
@aconran
Sencha Architect Development Team
-
21 Feb 2013 9:07 AM #6
Eric, nicely done on bug report details.
We've filed a bug. Well update you here when we know more.Phil Strong
@philstrong
#SenchaArchitect
Sencha Architect Development Team
You found a bug! We've classified it as
DSGNR-3368
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote