-
22 Jun 2012 5:07 PM #1
adding customConfig:null doesn''t work. Fix?
adding customConfig:null doesn''t work. Fix?
I need to use a customConfig. They way that I've seen it it needs to be declared as null so it can autogenerate the getters and setters. Adding a number instead of null works but null just doesn't. Is there a fix for this or do I need to leave Architect and start coding in the IDE?
-
25 Jun 2012 1:13 AM #2
-
25 Jun 2012 10:19 AM #3
I like the bump for glory!
I think for now the number e.g. 0 will have to do.
In the future you'll be able to create custom configs that are of literal type and will simply spit out what you wantPhil Strong
@philstrong
#SenchaArchitect
Sencha Architect Development Team
-
25 Jun 2012 12:15 PM #4
Thanks for the appreciation phil. So it shouldnt make any difference if i declare it as 0 right? The getters and setters are both created correctly for it.
-
29 Jun 2012 7:22 AM #5
You got it.
I do believe you need to call
of course if your getting getters and setters than this is happening either by your code or that of what your extending (framework)Code:constructor: function(config) { this.initConfig(config); },Phil Strong
@philstrong
#SenchaArchitect
Sencha Architect Development Team
-
29 Jun 2012 7:24 AM #6
As soon as I'm near my code I'll post it. Im not calling constructor.


Reply With Quote