On 12/14/2011 12:51 PM, thron7 wrote:
>
> On 12/14/2011 12:17 PM, Dietrich Streifert wrote:
>> Meanwhile I "solved?!?!?" the exception by moving the declaration of the
>> methods "extendClass" and "getKeys" up to qx.Bootstrap (starting on line
>> 64) right before method "define". Down at
>> qx.Bootstrap.define("qx.Bootstrap", I replaced the definitions of
>> "extendClass" and "getKeys" with:
>>
>> extendClass : qx.Bootstrap.extendClass,
>> getKeys : qx.Bootstrap.getKeys,
>>
>> Anyway: this is the stacktrace shown in Titanium Studio:
>>
>> qx.Bootstrap.define() [qx-oo-noopt.js:129]
>> (anonymous function)() [qx-oo-noopt.js:200]
>> (anonymous function)() [app.js:2]
>>
>> where qx-oo-noopt.js is loaded from app.js line 2.
Ah, now I see clearer. If you look at the code in 'define' these
delicate calls to extendClass and getKeys are guarded by checks for the
passed-in defining map (config.members and config.extend). But the map
passed in the qx.Bootstrap.define call (l.200) does not contain any of
those, hence these paths are never taken (and shouldn't in this case).
Could you check if there is a 'magic' "config" object hanging around on
Titanium/Android?
T.
------------------------------------------------------------------------------
Cloud Computing - Latest Buzzword or a Glimpse of the Future?
This paper surveys cloud computing today: What are the benefits?
Why are businesses embracing it? What are its payoffs and pitfalls?
http://www.accelacomm.com/jaw/sdnl/114/51425149/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
