I’m having trouble building a test case that exhibits the problem.

Here is the stack trace though in case it’s helpful…

set (Viewport.js:124)
org.apache.flex.utils.Language.superSetter (Language.js:329)
set (ScrollingViewport.js:98)
org.apache.flex.core.UIHTMLElementWrapper.addBead (UIHTMLElementWrapper.js:65)
childCtor.base (base.js:2435)
org.apache.flex.core.UIBase.addBead (UIBase.js:344)
org.apache.flex.core.UIBase.addedToParent (UIBase.js:518)
childCtor.base (base.js:2435)
org.apache.flex.core.ContainerBase.addedToParent (ContainerBase.js:165)
org.apache.flex.core.UIBase.addElement (UIBase.js:376)
childCtor.base (base.js:2435)
org.apache.flex.core.ContainerBase.addElement (ContainerBase.js:100)
org.apache.flex.utils.MXMLDataInterpreter.initializeStrandBasedObject 
(MXMLDataInterpreter.js:218)
org.apache.flex.utils.MXMLDataInterpreter.generateMXMLArray 
(MXMLDataInterpreter.js:116)
org.apache.flex.utils.MXMLDataInterpreter.generateMXMLInstances 
(MXMLDataInterpreter.js:252)
org.apache.flex.core.ContainerBase.addedToParent (ContainerBase.js:167)
org.apache.flex.core.UIBase.addElement (UIBase.js:376)
childCtor.base (base.js:2435)
org.apache.flex.core.ContainerBase.addElement (ContainerBase.js:100)
org.apache.flex.utils.MXMLDataInterpreter.initializeStrandBasedObject 
(MXMLDataInterpreter.js:218)
org.apache.flex.utils.MXMLDataInterpreter.generateMXMLArray 
(MXMLDataInterpreter.js:116)
org.apache.flex.utils.MXMLDataInterpreter.generateMXMLInstances 
(MXMLDataInterpreter.js:252)
org.apache.flex.core.ContainerBase.addedToParent (ContainerBase.js:167)
org.apache.flex.core.Application.addElement (Application.js:150)
org.apache.flex.core.Application.initialize (Application.js:64)
org.apache.flex.core.Application.start (Application.js:274)
(anonymous function) (VM1679 index.html:500)


On Sep 8, 2016, at 11:01 PM, Harbs <harbs.li...@gmail.com> wrote:

> It’s in my app.
> 
> I’ll see if I can distill the problem.
> 
> On Sep 8, 2016, at 10:47 PM, Alex Harui <aha...@adobe.com> wrote:
> 
>> OK, then there is some issue I haven't seen before.
>> 
>> What example is having this problem, and is it only the version in
>> sprite-refactor?
>> 
>> -Alex
>> 
>> On 9/8/16, 12:32 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>> 
>>> DataBindingExample works.
>>> 
>>> On Sep 8, 2016, at 10:18 PM, Alex Harui <aha...@adobe.com> wrote:
>>> 
>>>> Can the latest falcon compile and run DataBindingExample in the develop
>>>> branch and/or the refactor-sprite branch or is DataBindingExample having
>>>> the same problem?
>>>> 
>>>> On 9/8/16, 12:13 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>>>> 
>>>>> Yes.
>>>>> 
>>>>> My original problem was with ICSSImpl, but I resolved that. My problem
>>>>> is
>>>>> no longer the CSS file (which I now have). It’s now that I cannot get
>>>>> the
>>>>> iContentView because SimpleCSSValuesImpl does not find it.
>>>>> 
>>>>> On Sep 8, 2016, at 10:08 PM, Alex Harui <aha...@adobe.com> wrote:
>>>>> 
>>>>>> The latest Falcon is expecting to find a new interface in the JS
>>>>>> dependencies and uses that to determine whether to output CSS
>>>>>> information.
>>>>>> 
>>>>>> In the bin/js-debug, is there an ICSSImpl.js file?
>>>>>> 
>>>>>> -Alex
>>>>>> 
>>>>>> On 9/8/16, 12:00 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>>>>>> 
>>>>>>> I’m working off the refactor-sprite branch which has all the latest
>>>>>>> changes from develop. (I merged it today.)
>>>>>>> 
>>>>>>> When I compile against the Falcon 0.7.0 release, I get no errors. If
>>>>>>> I
>>>>>>> compile against the latest Falcon develop branch, I get this error.
>>>>>>> This
>>>>>>> is both using the same asjs code (latest refactor-sprite).
>>>>>>> 
>>>>>>> On Sep 8, 2016, at 6:05 PM, Alex Harui <aha...@adobe.com> wrote:
>>>>>>> 
>>>>>>>> Are you working on a branch in flex-asjs?  Have you synched that
>>>>>>>> branch
>>>>>>>> against flex-asjs develop branch?
>>>>>>>> 
>>>>>>>> -Alex
>>>>>>>> 
>>>>>>>> On 9/8/16, 2:42 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>>>>>>>> 
>>>>>>>>> I’m getting an error when compiling my app with the latest build of
>>>>>>>>> Falcon which I’m not seeing in the 0.7.0 release:
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Object.defineProperties(org.apache.flex.html.supportClasses.Viewport
>>>>>>>>> .p
>>>>>>>>> ro
>>>>>>>>> to
>>>>>>>>> type, /** @lends
>>>>>>>>> {org.apache.flex.html.supportClasses.Viewport.prototype}
>>>>>>>>> */ {
>>>>>>>>> /** @export */
>>>>>>>>> contentView: {
>>>>>>>>> get: /** @this {org.apache.flex.html.supportClasses.Viewport} */
>>>>>>>>> function() {
>>>>>>>>> return this.contentArea;
>>>>>>>>> }},
>>>>>>>>> /** @export */
>>>>>>>>> strand: {
>>>>>>>>> set: /** @this {org.apache.flex.html.supportClasses.Viewport} */
>>>>>>>>> function(value) {
>>>>>>>>> this._strand = value;
>>>>>>>>> this.contentArea =
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> org.apache.flex.utils.Language.as(this._strand.getBeadByType(org.apa
>>>>>>>>> ch
>>>>>>>>> e.
>>>>>>>>> fl
>>>>>>>>> ex.core.IContentView), org.apache.flex.core.UIBase);
>>>>>>>>> if (!this.contentArea) {
>>>>>>>>> var /** @type {Object} */ c =
>>>>>>>>> 
>>>>>>>>> org.apache.flex.core.ValuesManager.valuesImpl.getValue(this._strand,
>>>>>>>>> 'iContentView');
>>>>>>>>> this.contentArea = org.apache.flex.utils.Language.as(new c(),
>>>>>>>>> org.apache.flex.core.UIBase);
>>>>>>>>> }
>>>>>>>>> }}}
>>>>>>>>> );
>>>>>>>>> 
>>>>>>>>> In the above cross-compiled code, the contentArea bead is not
>>>>>>>>> defined.
>>>>>>>>> That seems to be OK. The problem is that c is undefined as well
>>>>>>>>> because
>>>>>>>>> the SimpleCSSValuesImpl cannot get the iContentView from the strand
>>>>>>>>> which
>>>>>>>>> is a org.apache.flex.html.Container.
>>>>>>>>> 
>>>>>>>>> The iContentView should be a
>>>>>>>>> org.apache.flex.html.supportClasses.ContainerContentArea as defined
>>>>>>>>> in
>>>>>>>>> the HTML defaults.css file.
>>>>>>>>> 
>>>>>>>>> I’m not sure what changed in Falcon which would cause this. I
>>>>>>>>> assume
>>>>>>>>> it’s
>>>>>>>>> from changes made by either Alex or Greg.
>>>>>>>>> 
>>>>>>>>> Suggestions?
>>>>>>>>> 
>>>>>>>>> Harbs
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
> 

Reply via email to