You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by OmPrakash Muppirala <bi...@gmail.com> on 2013/09/19 06:58:29 UTC
[FlexJS] StatesTest example app broken?
I picked this project up [1] after a while and when I run the app, I am
getting this RTE:
TypeError: Error #1009: Cannot access a property or method of a null object
reference.
at org.apache.flex.core::ViewBase/set
states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\as\src\org\apache\flex\core\ViewBase.as:83]
at
MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\StatesTest\src\MyInitialView.mxml:23]
at StatesTest/_StatesTest_MyInitialView1_c()
at
StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\StatesTest\src\StatesTest.mxml:26]
I resynced recently and I am guessing some recent changes break this app.
When I step through the debugger, it looks like ValuesManager.valuesImpl is
returning null.
Alex/Peter, can one of you please take a look?
Thanks,
Om
[1] https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTest
Re: [FlexJS] StatesTest example app broken?
Posted by Alex Harui <ah...@adobe.com>.
On 9/20/13 10:53 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>Before we decide to work on a FlexJS 'alpha' version, the process of
>actually building an app needs to be way more accessible.
For sure.
>Maybe we
>should abandon Flash Builder and start to work with a tool that's a
>bit more 'open', which we are able to modify/adapt for a more
>transparent workflow? Ideas?
My current plan is to spend a bit more time on FB. I was going to look
into an compiler option that will look for FB properties files in the
project folder and thus get more of it right.
But it sure would be interesting to see the IntelliJ folks get involved.
And any other tool would be great if folks have interest.
I still think direct FB integration is going to be a boatload of work so
the alpha will have to use external tools, I just want to make those tools
a bit smarter.
I've also wanted to do more tools that generate the basic template for an
Application or View. It would be great to see folks work on that if they
have cycles.
-Alex
Re: [FlexJS] StatesTest example app broken?
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Before we decide to work on a FlexJS 'alpha' version, the process of
actually building an app needs to be way more accessible. Maybe we
should abandon Flash Builder and start to work with a tool that's a
bit more 'open', which we are able to modify/adapt for a more
transparent workflow? Ideas?
EdB
On Fri, Sep 20, 2013 at 7:48 PM, Peter Ent <pe...@adobe.com> wrote:
> With a little direction from Alex, I'm able to run the app too. Here's
> what happened to me:
>
> I created a new Flex project and then imported the code from
> DataBindingTest. I deleted the default application Flash Builder created
> and I then changed the project's properties and made DataBindingTest.mxml
> an Application and made it the default application.
>
> Cannot do that. Flash Builder still uses mxmlc to compile that.
>
> To fix this, I renamed DataBindingTest.mxml to my project's original
> default application name, selected it and built it with the FlexJS
> external tool and now it works correctly.
>
> --peter
>
> On 9/19/13 3:04 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
>>I stepped through my working copy of DataBindingTest.
>>
>>The initHandler in Application.as gets called first, and sets up the
>>ValueManager. Then, the MyInitialView gets addedToParent, which fires off
>>the MXMLDataIntepreter which assigns the states.
>>
>>Which made me look at the call stack and again, there is the dreaded
>>XXX_c() which means that Falcon did not compile the SWF, MXMLC did.
>>
>>-Alex
>>
>>On 9/19/13 10:58 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>
>>>As far as I can tell, this is what is happening:
>>>
>>>"states" is a property of ViewBase and the property is being set very
>>>quickly upon application load. The states setter function is assuming
>>>there is a valuesImpl loaded into the ValuesManager, but that's not the
>>>case because the Application's initHandler hasn't been called yet and it
>>>is there that valuesImpl is set in the ValuesManager.
>>>
>>>Not sure yet how to deal with this, but I will work on it.
>>>
>>>--peter
>>>
>>>On 9/19/13 12:09 PM, "Alex Harui" <ah...@adobe.com> wrote:
>>>
>>>>I'll let you do the digging, but make sure the capitalization is right,
>>>>and that it is using the same ValuesImpl as DataBindingTest.
>>>>
>>>>On 9/19/13 9:02 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>>>
>>>>>I'm not making any headway on this. There is a global style declaration
>>>>>which should associate a state implementation with any class:
>>>>>
>>>>>global
>>>>>{
>>>>> iStatesImpl:
>>>>>ClassReference("org.apache.flex.core.SimpleStatesImpl");
>>>>>}
>>>>>
>>>>>
>>>>>I don't know why this isn't being picked up. I'm going to try
>>>>>DataBindingTest and see how that goes.
>>>>>--peter
>>>>>
>>>>>On 9/19/13 11:12 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>>>>
>>>>>>I am looking into this.
>>>>>>--peter
>>>>>>
>>>>>>On 9/19/13 1:03 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>>>>
>>>>>>>I haven't tried StatesTest in a while. Can you work with
>>>>>>>DataBindingTest
>>>>>>>instead? It should have everything StatesTest has and more.
>>>>>>>
>>>>>>>-Alex
>>>>>>>
>>>>>>>On 9/18/13 9:58 PM, "OmPrakash Muppirala" <bi...@gmail.com>
>>>>>>>wrote:
>>>>>>>
>>>>>>>>I picked this project up [1] after a while and when I run the app, I
>>>>>>>>am
>>>>>>>>getting this RTE:
>>>>>>>>
>>>>>>>>TypeError: Error #1009: Cannot access a property or method of a null
>>>>>>>>object
>>>>>>>>reference.
>>>>>>>> at org.apache.flex.core::ViewBase/set
>>>>>>>>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\as
>>>>>>>>\
>>>>>>>>s
>>>>>>>>r
>>>>>>>>c
>>>>>>>>\
>>>>>>>>o
>>>>>>>>rg\apache\flex\core\ViewBase.as:83]
>>>>>>>> at
>>>>>>>>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\exampl
>>>>>>>>e
>>>>>>>>s
>>>>>>>>\
>>>>>>>>S
>>>>>>>>t
>>>>>>>>a
>>>>>>>>tesTest\src\MyInitialView.mxml:23]
>>>>>>>> at StatesTest/_StatesTest_MyInitialView1_c()
>>>>>>>> at
>>>>>>>>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\
>>>>>>>>S
>>>>>>>>t
>>>>>>>>a
>>>>>>>>t
>>>>>>>>e
>>>>>>>>s
>>>>>>>>Test\src\StatesTest.mxml:26]
>>>>>>>>
>>>>>>>>I resynced recently and I am guessing some recent changes break this
>>>>>>>>app.
>>>>>>>>When I step through the debugger, it looks like
>>>>>>>>ValuesManager.valuesImpl
>>>>>>>>is
>>>>>>>>returning null.
>>>>>>>>
>>>>>>>>Alex/Peter, can one of you please take a look?
>>>>>>>>
>>>>>>>>Thanks,
>>>>>>>>Om
>>>>>>>>
>>>>>>>>[1]
>>>>>>>>https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTest
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [FlexJS] StatesTest example app broken?
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Fri, Sep 20, 2013 at 5:40 PM, Alex Harui <ah...@adobe.com> wrote:
> Maybe I'm not understanding what Peter wrote, but I think he also said
> that it worked once the main app matched the project name. IOW, if you
> create a FlexProject called OmTest, then when you copy the code from
> DataBindingTest.mxml, you should copy that into your OmTest.mxml. You
> should have to fix up the MyController.as and a few other places that
> assume the name of the app. Then MXMLC should compile that when you save
> everything. But then you click on OmTest.mxml in the Package Explorer and
> run the external tool and it should replace the SWF in the bin-debug. And
> then when you choose Debug As,
So far so good. This is exactly what I am doing...
> it shouldn't run MXMLC again, it should
> just launch the SWF.
>
>
But, it looks like mxmlc is overwriting the swf just before launching.
> I wonder if there is a file date problem fooling MXMLC into running again.
>
>
Probably. How would I test that?
In any case, I am good for now. I am unblocked and have been able to make
progress in what I have been trying to do. I dont want to waste your time
anymore, especially since you have plans of making the workflow better.
Let me know how I can help.
Thanks,
Om
> -Alex
>
> On 9/20/13 5:30 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
> >On Fri, Sep 20, 2013 at 5:23 PM, Alex Harui <ah...@adobe.com> wrote:
> >
> >> In theory, if the project name matches the application.mxml name, then
> >>the
> >> external tool should overwrite the swf and you shouldn't need to mess
> >> around with the external tools and templates.
> >>
> >
> >The problem is what Peter explained. The debug launch causes mxmlc to
> >compile the swf just before launching. Altering the name keeps the falcon
> >compiled swf intact.
> >
> >Thanks,
> >Om
> >
> >
> >>
> >> Is that not working for you or does the application name have a
> >>different
> >> name than the project?
> >>
> >> Thanks,
> >> -Alex
> >>
> >> On 9/20/13 4:14 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
> >>
> >> >I fixed this for myself by doing this:
> >> >
> >> >In the FlexJS debug and release build external tool's arguments:
> >> >Change:
> >> >-output="${project_loc}\bin-debug\${project_name}.swf"
> >> >to:
> >> >-output="${project_loc}\bin-debug\${project_name}_flexjs.swf"
> >> >
> >> >Then, for each FlexJS project, we need to change index.template's
> >>params
> >> >settings:
> >> >change:
> >> >"${swf}.swf", "flashContent",
> >> >to:
> >> >"${swf}_flexjs.swf", "flashContent",
> >> >
> >> >Now, when we run FB's debug option, project_name.swf gets created by
> >>mxmlc
> >> >but we will be running project_name_flexjs.swf which was compiled by
> >> >falcon. This should let us debug the app as usual.
> >> >
> >> >Thanks,
> >> >Om
> >> >
> >> >
> >> >
> >> >On Fri, Sep 20, 2013 at 10:48 AM, Peter Ent <pe...@adobe.com> wrote:
> >> >
> >> >> With a little direction from Alex, I'm able to run the app too.
> >>Here's
> >> >> what happened to me:
> >> >>
> >> >> I created a new Flex project and then imported the code from
> >> >> DataBindingTest. I deleted the default application Flash Builder
> >>created
> >> >> and I then changed the project's properties and made
> >> >>DataBindingTest.mxml
> >> >> an Application and made it the default application.
> >> >>
> >> >> Cannot do that. Flash Builder still uses mxmlc to compile that.
> >> >>
> >> >> To fix this, I renamed DataBindingTest.mxml to my project's original
> >> >> default application name, selected it and built it with the FlexJS
> >> >> external tool and now it works correctly.
> >> >>
> >> >> --peter
> >> >>
> >> >> On 9/19/13 3:04 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >> >>
> >> >> >I stepped through my working copy of DataBindingTest.
> >> >> >
> >> >> >The initHandler in Application.as gets called first, and sets up the
> >> >> >ValueManager. Then, the MyInitialView gets addedToParent, which
> >>fires
> >> >>off
> >> >> >the MXMLDataIntepreter which assigns the states.
> >> >> >
> >> >> >Which made me look at the call stack and again, there is the dreaded
> >> >> >XXX_c() which means that Falcon did not compile the SWF, MXMLC did.
> >> >> >
> >> >> >-Alex
> >> >> >
> >> >> >On 9/19/13 10:58 AM, "Peter Ent" <pe...@adobe.com> wrote:
> >> >> >
> >> >> >>As far as I can tell, this is what is happening:
> >> >> >>
> >> >> >>"states" is a property of ViewBase and the property is being set
> >>very
> >> >> >>quickly upon application load. The states setter function is
> >>assuming
> >> >> >>there is a valuesImpl loaded into the ValuesManager, but that's not
> >> >>the
> >> >> >>case because the Application's initHandler hasn't been called yet
> >>and
> >> >>it
> >> >> >>is there that valuesImpl is set in the ValuesManager.
> >> >> >>
> >> >> >>Not sure yet how to deal with this, but I will work on it.
> >> >> >>
> >> >> >>--peter
> >> >> >>
> >> >> >>On 9/19/13 12:09 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >> >> >>
> >> >> >>>I'll let you do the digging, but make sure the capitalization is
> >> >>right,
> >> >> >>>and that it is using the same ValuesImpl as DataBindingTest.
> >> >> >>>
> >> >> >>>On 9/19/13 9:02 AM, "Peter Ent" <pe...@adobe.com> wrote:
> >> >> >>>
> >> >> >>>>I'm not making any headway on this. There is a global style
> >> >>declaration
> >> >> >>>>which should associate a state implementation with any class:
> >> >> >>>>
> >> >> >>>>global
> >> >> >>>>{
> >> >> >>>> iStatesImpl:
> >> >> >>>>ClassReference("org.apache.flex.core.SimpleStatesImpl");
> >> >> >>>>}
> >> >> >>>>
> >> >> >>>>
> >> >> >>>>I don't know why this isn't being picked up. I'm going to try
> >> >> >>>>DataBindingTest and see how that goes.
> >> >> >>>>--peter
> >> >> >>>>
> >> >> >>>>On 9/19/13 11:12 AM, "Peter Ent" <pe...@adobe.com> wrote:
> >> >> >>>>
> >> >> >>>>>I am looking into this.
> >> >> >>>>>--peter
> >> >> >>>>>
> >> >> >>>>>On 9/19/13 1:03 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >> >> >>>>>
> >> >> >>>>>>I haven't tried StatesTest in a while. Can you work with
> >> >> >>>>>>DataBindingTest
> >> >> >>>>>>instead? It should have everything StatesTest has and more.
> >> >> >>>>>>
> >> >> >>>>>>-Alex
> >> >> >>>>>>
> >> >> >>>>>>On 9/18/13 9:58 PM, "OmPrakash Muppirala"
> >><bi...@gmail.com>
> >> >> >>>>>>wrote:
> >> >> >>>>>>
> >> >> >>>>>>>I picked this project up [1] after a while and when I run the
> >> >>app, I
> >> >> >>>>>>>am
> >> >> >>>>>>>getting this RTE:
> >> >> >>>>>>>
> >> >> >>>>>>>TypeError: Error #1009: Cannot access a property or method of
> >>a
> >> >>null
> >> >> >>>>>>>object
> >> >> >>>>>>>reference.
> >> >> >>>>>>> at org.apache.flex.core::ViewBase/set
> >> >>
> >>
> >>>>>>>>>>>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\framework
> >>>>>>>>>>>s\
> >> >>>>>>>>>as
> >> >> >>>>>>>\
> >> >> >>>>>>>s
> >> >> >>>>>>>r
> >> >> >>>>>>>c
> >> >> >>>>>>>\
> >> >> >>>>>>>o
> >> >> >>>>>>>rg\apache\flex\core\ViewBase.as:83]
> >> >> >>>>>>> at
> >> >>
> >>
> >>>>>>>>>>>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\ex
> >>>>>>>>>>>am
> >> >>>>>>>>>pl
> >> >> >>>>>>>e
> >> >> >>>>>>>s
> >> >> >>>>>>>\
> >> >> >>>>>>>S
> >> >> >>>>>>>t
> >> >> >>>>>>>a
> >> >> >>>>>>>tesTest\src\MyInitialView.mxml:23]
> >> >> >>>>>>> at StatesTest/_StatesTest_MyInitialView1_c()
> >> >> >>>>>>> at
> >> >>
> >>
> >>>>>>>>>>>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examp
> >>>>>>>>>>>le
> >> >>>>>>>>>s\
> >> >> >>>>>>>S
> >> >> >>>>>>>t
> >> >> >>>>>>>a
> >> >> >>>>>>>t
> >> >> >>>>>>>e
> >> >> >>>>>>>s
> >> >> >>>>>>>Test\src\StatesTest.mxml:26]
> >> >> >>>>>>>
> >> >> >>>>>>>I resynced recently and I am guessing some recent changes
> >>break
> >> >>this
> >> >> >>>>>>>app.
> >> >> >>>>>>>When I step through the debugger, it looks like
> >> >> >>>>>>>ValuesManager.valuesImpl
> >> >> >>>>>>>is
> >> >> >>>>>>>returning null.
> >> >> >>>>>>>
> >> >> >>>>>>>Alex/Peter, can one of you please take a look?
> >> >> >>>>>>>
> >> >> >>>>>>>Thanks,
> >> >> >>>>>>>Om
> >> >> >>>>>>>
> >> >> >>>>>>>[1]
> >> >>
> >> >>>>>>>>>
> >> https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTes
> >> >>>>>>>>>t
> >> >> >>>>>>
> >> >> >>>>>
> >> >> >>>>
> >> >> >>>
> >> >> >>
> >> >> >
> >> >>
> >> >>
> >>
> >>
>
>
Re: [FlexJS] StatesTest example app broken?
Posted by Alex Harui <ah...@adobe.com>.
Maybe I'm not understanding what Peter wrote, but I think he also said
that it worked once the main app matched the project name. IOW, if you
create a FlexProject called OmTest, then when you copy the code from
DataBindingTest.mxml, you should copy that into your OmTest.mxml. You
should have to fix up the MyController.as and a few other places that
assume the name of the app. Then MXMLC should compile that when you save
everything. But then you click on OmTest.mxml in the Package Explorer and
run the external tool and it should replace the SWF in the bin-debug. And
then when you choose Debug As, it shouldn't run MXMLC again, it should
just launch the SWF.
I wonder if there is a file date problem fooling MXMLC into running again.
-Alex
On 9/20/13 5:30 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>On Fri, Sep 20, 2013 at 5:23 PM, Alex Harui <ah...@adobe.com> wrote:
>
>> In theory, if the project name matches the application.mxml name, then
>>the
>> external tool should overwrite the swf and you shouldn't need to mess
>> around with the external tools and templates.
>>
>
>The problem is what Peter explained. The debug launch causes mxmlc to
>compile the swf just before launching. Altering the name keeps the falcon
>compiled swf intact.
>
>Thanks,
>Om
>
>
>>
>> Is that not working for you or does the application name have a
>>different
>> name than the project?
>>
>> Thanks,
>> -Alex
>>
>> On 9/20/13 4:14 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>
>> >I fixed this for myself by doing this:
>> >
>> >In the FlexJS debug and release build external tool's arguments:
>> >Change:
>> >-output="${project_loc}\bin-debug\${project_name}.swf"
>> >to:
>> >-output="${project_loc}\bin-debug\${project_name}_flexjs.swf"
>> >
>> >Then, for each FlexJS project, we need to change index.template's
>>params
>> >settings:
>> >change:
>> >"${swf}.swf", "flashContent",
>> >to:
>> >"${swf}_flexjs.swf", "flashContent",
>> >
>> >Now, when we run FB's debug option, project_name.swf gets created by
>>mxmlc
>> >but we will be running project_name_flexjs.swf which was compiled by
>> >falcon. This should let us debug the app as usual.
>> >
>> >Thanks,
>> >Om
>> >
>> >
>> >
>> >On Fri, Sep 20, 2013 at 10:48 AM, Peter Ent <pe...@adobe.com> wrote:
>> >
>> >> With a little direction from Alex, I'm able to run the app too.
>>Here's
>> >> what happened to me:
>> >>
>> >> I created a new Flex project and then imported the code from
>> >> DataBindingTest. I deleted the default application Flash Builder
>>created
>> >> and I then changed the project's properties and made
>> >>DataBindingTest.mxml
>> >> an Application and made it the default application.
>> >>
>> >> Cannot do that. Flash Builder still uses mxmlc to compile that.
>> >>
>> >> To fix this, I renamed DataBindingTest.mxml to my project's original
>> >> default application name, selected it and built it with the FlexJS
>> >> external tool and now it works correctly.
>> >>
>> >> --peter
>> >>
>> >> On 9/19/13 3:04 PM, "Alex Harui" <ah...@adobe.com> wrote:
>> >>
>> >> >I stepped through my working copy of DataBindingTest.
>> >> >
>> >> >The initHandler in Application.as gets called first, and sets up the
>> >> >ValueManager. Then, the MyInitialView gets addedToParent, which
>>fires
>> >>off
>> >> >the MXMLDataIntepreter which assigns the states.
>> >> >
>> >> >Which made me look at the call stack and again, there is the dreaded
>> >> >XXX_c() which means that Falcon did not compile the SWF, MXMLC did.
>> >> >
>> >> >-Alex
>> >> >
>> >> >On 9/19/13 10:58 AM, "Peter Ent" <pe...@adobe.com> wrote:
>> >> >
>> >> >>As far as I can tell, this is what is happening:
>> >> >>
>> >> >>"states" is a property of ViewBase and the property is being set
>>very
>> >> >>quickly upon application load. The states setter function is
>>assuming
>> >> >>there is a valuesImpl loaded into the ValuesManager, but that's not
>> >>the
>> >> >>case because the Application's initHandler hasn't been called yet
>>and
>> >>it
>> >> >>is there that valuesImpl is set in the ValuesManager.
>> >> >>
>> >> >>Not sure yet how to deal with this, but I will work on it.
>> >> >>
>> >> >>--peter
>> >> >>
>> >> >>On 9/19/13 12:09 PM, "Alex Harui" <ah...@adobe.com> wrote:
>> >> >>
>> >> >>>I'll let you do the digging, but make sure the capitalization is
>> >>right,
>> >> >>>and that it is using the same ValuesImpl as DataBindingTest.
>> >> >>>
>> >> >>>On 9/19/13 9:02 AM, "Peter Ent" <pe...@adobe.com> wrote:
>> >> >>>
>> >> >>>>I'm not making any headway on this. There is a global style
>> >>declaration
>> >> >>>>which should associate a state implementation with any class:
>> >> >>>>
>> >> >>>>global
>> >> >>>>{
>> >> >>>> iStatesImpl:
>> >> >>>>ClassReference("org.apache.flex.core.SimpleStatesImpl");
>> >> >>>>}
>> >> >>>>
>> >> >>>>
>> >> >>>>I don't know why this isn't being picked up. I'm going to try
>> >> >>>>DataBindingTest and see how that goes.
>> >> >>>>--peter
>> >> >>>>
>> >> >>>>On 9/19/13 11:12 AM, "Peter Ent" <pe...@adobe.com> wrote:
>> >> >>>>
>> >> >>>>>I am looking into this.
>> >> >>>>>--peter
>> >> >>>>>
>> >> >>>>>On 9/19/13 1:03 AM, "Alex Harui" <ah...@adobe.com> wrote:
>> >> >>>>>
>> >> >>>>>>I haven't tried StatesTest in a while. Can you work with
>> >> >>>>>>DataBindingTest
>> >> >>>>>>instead? It should have everything StatesTest has and more.
>> >> >>>>>>
>> >> >>>>>>-Alex
>> >> >>>>>>
>> >> >>>>>>On 9/18/13 9:58 PM, "OmPrakash Muppirala"
>><bi...@gmail.com>
>> >> >>>>>>wrote:
>> >> >>>>>>
>> >> >>>>>>>I picked this project up [1] after a while and when I run the
>> >>app, I
>> >> >>>>>>>am
>> >> >>>>>>>getting this RTE:
>> >> >>>>>>>
>> >> >>>>>>>TypeError: Error #1009: Cannot access a property or method of
>>a
>> >>null
>> >> >>>>>>>object
>> >> >>>>>>>reference.
>> >> >>>>>>> at org.apache.flex.core::ViewBase/set
>> >>
>>
>>>>>>>>>>>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\framework
>>>>>>>>>>>s\
>> >>>>>>>>>as
>> >> >>>>>>>\
>> >> >>>>>>>s
>> >> >>>>>>>r
>> >> >>>>>>>c
>> >> >>>>>>>\
>> >> >>>>>>>o
>> >> >>>>>>>rg\apache\flex\core\ViewBase.as:83]
>> >> >>>>>>> at
>> >>
>>
>>>>>>>>>>>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\ex
>>>>>>>>>>>am
>> >>>>>>>>>pl
>> >> >>>>>>>e
>> >> >>>>>>>s
>> >> >>>>>>>\
>> >> >>>>>>>S
>> >> >>>>>>>t
>> >> >>>>>>>a
>> >> >>>>>>>tesTest\src\MyInitialView.mxml:23]
>> >> >>>>>>> at StatesTest/_StatesTest_MyInitialView1_c()
>> >> >>>>>>> at
>> >>
>>
>>>>>>>>>>>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examp
>>>>>>>>>>>le
>> >>>>>>>>>s\
>> >> >>>>>>>S
>> >> >>>>>>>t
>> >> >>>>>>>a
>> >> >>>>>>>t
>> >> >>>>>>>e
>> >> >>>>>>>s
>> >> >>>>>>>Test\src\StatesTest.mxml:26]
>> >> >>>>>>>
>> >> >>>>>>>I resynced recently and I am guessing some recent changes
>>break
>> >>this
>> >> >>>>>>>app.
>> >> >>>>>>>When I step through the debugger, it looks like
>> >> >>>>>>>ValuesManager.valuesImpl
>> >> >>>>>>>is
>> >> >>>>>>>returning null.
>> >> >>>>>>>
>> >> >>>>>>>Alex/Peter, can one of you please take a look?
>> >> >>>>>>>
>> >> >>>>>>>Thanks,
>> >> >>>>>>>Om
>> >> >>>>>>>
>> >> >>>>>>>[1]
>> >>
>> >>>>>>>>>
>> https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTes
>> >>>>>>>>>t
>> >> >>>>>>
>> >> >>>>>
>> >> >>>>
>> >> >>>
>> >> >>
>> >> >
>> >>
>> >>
>>
>>
Re: [FlexJS] StatesTest example app broken?
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Fri, Sep 20, 2013 at 5:23 PM, Alex Harui <ah...@adobe.com> wrote:
> In theory, if the project name matches the application.mxml name, then the
> external tool should overwrite the swf and you shouldn't need to mess
> around with the external tools and templates.
>
The problem is what Peter explained. The debug launch causes mxmlc to
compile the swf just before launching. Altering the name keeps the falcon
compiled swf intact.
Thanks,
Om
>
> Is that not working for you or does the application name have a different
> name than the project?
>
> Thanks,
> -Alex
>
> On 9/20/13 4:14 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
> >I fixed this for myself by doing this:
> >
> >In the FlexJS debug and release build external tool's arguments:
> >Change:
> >-output="${project_loc}\bin-debug\${project_name}.swf"
> >to:
> >-output="${project_loc}\bin-debug\${project_name}_flexjs.swf"
> >
> >Then, for each FlexJS project, we need to change index.template's params
> >settings:
> >change:
> >"${swf}.swf", "flashContent",
> >to:
> >"${swf}_flexjs.swf", "flashContent",
> >
> >Now, when we run FB's debug option, project_name.swf gets created by mxmlc
> >but we will be running project_name_flexjs.swf which was compiled by
> >falcon. This should let us debug the app as usual.
> >
> >Thanks,
> >Om
> >
> >
> >
> >On Fri, Sep 20, 2013 at 10:48 AM, Peter Ent <pe...@adobe.com> wrote:
> >
> >> With a little direction from Alex, I'm able to run the app too. Here's
> >> what happened to me:
> >>
> >> I created a new Flex project and then imported the code from
> >> DataBindingTest. I deleted the default application Flash Builder created
> >> and I then changed the project's properties and made
> >>DataBindingTest.mxml
> >> an Application and made it the default application.
> >>
> >> Cannot do that. Flash Builder still uses mxmlc to compile that.
> >>
> >> To fix this, I renamed DataBindingTest.mxml to my project's original
> >> default application name, selected it and built it with the FlexJS
> >> external tool and now it works correctly.
> >>
> >> --peter
> >>
> >> On 9/19/13 3:04 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >>
> >> >I stepped through my working copy of DataBindingTest.
> >> >
> >> >The initHandler in Application.as gets called first, and sets up the
> >> >ValueManager. Then, the MyInitialView gets addedToParent, which fires
> >>off
> >> >the MXMLDataIntepreter which assigns the states.
> >> >
> >> >Which made me look at the call stack and again, there is the dreaded
> >> >XXX_c() which means that Falcon did not compile the SWF, MXMLC did.
> >> >
> >> >-Alex
> >> >
> >> >On 9/19/13 10:58 AM, "Peter Ent" <pe...@adobe.com> wrote:
> >> >
> >> >>As far as I can tell, this is what is happening:
> >> >>
> >> >>"states" is a property of ViewBase and the property is being set very
> >> >>quickly upon application load. The states setter function is assuming
> >> >>there is a valuesImpl loaded into the ValuesManager, but that's not
> >>the
> >> >>case because the Application's initHandler hasn't been called yet and
> >>it
> >> >>is there that valuesImpl is set in the ValuesManager.
> >> >>
> >> >>Not sure yet how to deal with this, but I will work on it.
> >> >>
> >> >>--peter
> >> >>
> >> >>On 9/19/13 12:09 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >> >>
> >> >>>I'll let you do the digging, but make sure the capitalization is
> >>right,
> >> >>>and that it is using the same ValuesImpl as DataBindingTest.
> >> >>>
> >> >>>On 9/19/13 9:02 AM, "Peter Ent" <pe...@adobe.com> wrote:
> >> >>>
> >> >>>>I'm not making any headway on this. There is a global style
> >>declaration
> >> >>>>which should associate a state implementation with any class:
> >> >>>>
> >> >>>>global
> >> >>>>{
> >> >>>> iStatesImpl:
> >> >>>>ClassReference("org.apache.flex.core.SimpleStatesImpl");
> >> >>>>}
> >> >>>>
> >> >>>>
> >> >>>>I don't know why this isn't being picked up. I'm going to try
> >> >>>>DataBindingTest and see how that goes.
> >> >>>>--peter
> >> >>>>
> >> >>>>On 9/19/13 11:12 AM, "Peter Ent" <pe...@adobe.com> wrote:
> >> >>>>
> >> >>>>>I am looking into this.
> >> >>>>>--peter
> >> >>>>>
> >> >>>>>On 9/19/13 1:03 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >> >>>>>
> >> >>>>>>I haven't tried StatesTest in a while. Can you work with
> >> >>>>>>DataBindingTest
> >> >>>>>>instead? It should have everything StatesTest has and more.
> >> >>>>>>
> >> >>>>>>-Alex
> >> >>>>>>
> >> >>>>>>On 9/18/13 9:58 PM, "OmPrakash Muppirala" <bi...@gmail.com>
> >> >>>>>>wrote:
> >> >>>>>>
> >> >>>>>>>I picked this project up [1] after a while and when I run the
> >>app, I
> >> >>>>>>>am
> >> >>>>>>>getting this RTE:
> >> >>>>>>>
> >> >>>>>>>TypeError: Error #1009: Cannot access a property or method of a
> >>null
> >> >>>>>>>object
> >> >>>>>>>reference.
> >> >>>>>>> at org.apache.flex.core::ViewBase/set
> >>
> >>>>>>>>>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\
> >>>>>>>>>as
> >> >>>>>>>\
> >> >>>>>>>s
> >> >>>>>>>r
> >> >>>>>>>c
> >> >>>>>>>\
> >> >>>>>>>o
> >> >>>>>>>rg\apache\flex\core\ViewBase.as:83]
> >> >>>>>>> at
> >>
> >>>>>>>>>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\exam
> >>>>>>>>>pl
> >> >>>>>>>e
> >> >>>>>>>s
> >> >>>>>>>\
> >> >>>>>>>S
> >> >>>>>>>t
> >> >>>>>>>a
> >> >>>>>>>tesTest\src\MyInitialView.mxml:23]
> >> >>>>>>> at StatesTest/_StatesTest_MyInitialView1_c()
> >> >>>>>>> at
> >>
> >>>>>>>>>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\example
> >>>>>>>>>s\
> >> >>>>>>>S
> >> >>>>>>>t
> >> >>>>>>>a
> >> >>>>>>>t
> >> >>>>>>>e
> >> >>>>>>>s
> >> >>>>>>>Test\src\StatesTest.mxml:26]
> >> >>>>>>>
> >> >>>>>>>I resynced recently and I am guessing some recent changes break
> >>this
> >> >>>>>>>app.
> >> >>>>>>>When I step through the debugger, it looks like
> >> >>>>>>>ValuesManager.valuesImpl
> >> >>>>>>>is
> >> >>>>>>>returning null.
> >> >>>>>>>
> >> >>>>>>>Alex/Peter, can one of you please take a look?
> >> >>>>>>>
> >> >>>>>>>Thanks,
> >> >>>>>>>Om
> >> >>>>>>>
> >> >>>>>>>[1]
> >>
> >>>>>>>>>
> https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTes
> >>>>>>>>>t
> >> >>>>>>
> >> >>>>>
> >> >>>>
> >> >>>
> >> >>
> >> >
> >>
> >>
>
>
Re: [FlexJS] StatesTest example app broken?
Posted by Alex Harui <ah...@adobe.com>.
In theory, if the project name matches the application.mxml name, then the
external tool should overwrite the swf and you shouldn't need to mess
around with the external tools and templates.
Is that not working for you or does the application name have a different
name than the project?
Thanks,
-Alex
On 9/20/13 4:14 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>I fixed this for myself by doing this:
>
>In the FlexJS debug and release build external tool's arguments:
>Change:
>-output="${project_loc}\bin-debug\${project_name}.swf"
>to:
>-output="${project_loc}\bin-debug\${project_name}_flexjs.swf"
>
>Then, for each FlexJS project, we need to change index.template's params
>settings:
>change:
>"${swf}.swf", "flashContent",
>to:
>"${swf}_flexjs.swf", "flashContent",
>
>Now, when we run FB's debug option, project_name.swf gets created by mxmlc
>but we will be running project_name_flexjs.swf which was compiled by
>falcon. This should let us debug the app as usual.
>
>Thanks,
>Om
>
>
>
>On Fri, Sep 20, 2013 at 10:48 AM, Peter Ent <pe...@adobe.com> wrote:
>
>> With a little direction from Alex, I'm able to run the app too. Here's
>> what happened to me:
>>
>> I created a new Flex project and then imported the code from
>> DataBindingTest. I deleted the default application Flash Builder created
>> and I then changed the project's properties and made
>>DataBindingTest.mxml
>> an Application and made it the default application.
>>
>> Cannot do that. Flash Builder still uses mxmlc to compile that.
>>
>> To fix this, I renamed DataBindingTest.mxml to my project's original
>> default application name, selected it and built it with the FlexJS
>> external tool and now it works correctly.
>>
>> --peter
>>
>> On 9/19/13 3:04 PM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>> >I stepped through my working copy of DataBindingTest.
>> >
>> >The initHandler in Application.as gets called first, and sets up the
>> >ValueManager. Then, the MyInitialView gets addedToParent, which fires
>>off
>> >the MXMLDataIntepreter which assigns the states.
>> >
>> >Which made me look at the call stack and again, there is the dreaded
>> >XXX_c() which means that Falcon did not compile the SWF, MXMLC did.
>> >
>> >-Alex
>> >
>> >On 9/19/13 10:58 AM, "Peter Ent" <pe...@adobe.com> wrote:
>> >
>> >>As far as I can tell, this is what is happening:
>> >>
>> >>"states" is a property of ViewBase and the property is being set very
>> >>quickly upon application load. The states setter function is assuming
>> >>there is a valuesImpl loaded into the ValuesManager, but that's not
>>the
>> >>case because the Application's initHandler hasn't been called yet and
>>it
>> >>is there that valuesImpl is set in the ValuesManager.
>> >>
>> >>Not sure yet how to deal with this, but I will work on it.
>> >>
>> >>--peter
>> >>
>> >>On 9/19/13 12:09 PM, "Alex Harui" <ah...@adobe.com> wrote:
>> >>
>> >>>I'll let you do the digging, but make sure the capitalization is
>>right,
>> >>>and that it is using the same ValuesImpl as DataBindingTest.
>> >>>
>> >>>On 9/19/13 9:02 AM, "Peter Ent" <pe...@adobe.com> wrote:
>> >>>
>> >>>>I'm not making any headway on this. There is a global style
>>declaration
>> >>>>which should associate a state implementation with any class:
>> >>>>
>> >>>>global
>> >>>>{
>> >>>> iStatesImpl:
>> >>>>ClassReference("org.apache.flex.core.SimpleStatesImpl");
>> >>>>}
>> >>>>
>> >>>>
>> >>>>I don't know why this isn't being picked up. I'm going to try
>> >>>>DataBindingTest and see how that goes.
>> >>>>--peter
>> >>>>
>> >>>>On 9/19/13 11:12 AM, "Peter Ent" <pe...@adobe.com> wrote:
>> >>>>
>> >>>>>I am looking into this.
>> >>>>>--peter
>> >>>>>
>> >>>>>On 9/19/13 1:03 AM, "Alex Harui" <ah...@adobe.com> wrote:
>> >>>>>
>> >>>>>>I haven't tried StatesTest in a while. Can you work with
>> >>>>>>DataBindingTest
>> >>>>>>instead? It should have everything StatesTest has and more.
>> >>>>>>
>> >>>>>>-Alex
>> >>>>>>
>> >>>>>>On 9/18/13 9:58 PM, "OmPrakash Muppirala" <bi...@gmail.com>
>> >>>>>>wrote:
>> >>>>>>
>> >>>>>>>I picked this project up [1] after a while and when I run the
>>app, I
>> >>>>>>>am
>> >>>>>>>getting this RTE:
>> >>>>>>>
>> >>>>>>>TypeError: Error #1009: Cannot access a property or method of a
>>null
>> >>>>>>>object
>> >>>>>>>reference.
>> >>>>>>> at org.apache.flex.core::ViewBase/set
>>
>>>>>>>>>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\
>>>>>>>>>as
>> >>>>>>>\
>> >>>>>>>s
>> >>>>>>>r
>> >>>>>>>c
>> >>>>>>>\
>> >>>>>>>o
>> >>>>>>>rg\apache\flex\core\ViewBase.as:83]
>> >>>>>>> at
>>
>>>>>>>>>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\exam
>>>>>>>>>pl
>> >>>>>>>e
>> >>>>>>>s
>> >>>>>>>\
>> >>>>>>>S
>> >>>>>>>t
>> >>>>>>>a
>> >>>>>>>tesTest\src\MyInitialView.mxml:23]
>> >>>>>>> at StatesTest/_StatesTest_MyInitialView1_c()
>> >>>>>>> at
>>
>>>>>>>>>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\example
>>>>>>>>>s\
>> >>>>>>>S
>> >>>>>>>t
>> >>>>>>>a
>> >>>>>>>t
>> >>>>>>>e
>> >>>>>>>s
>> >>>>>>>Test\src\StatesTest.mxml:26]
>> >>>>>>>
>> >>>>>>>I resynced recently and I am guessing some recent changes break
>>this
>> >>>>>>>app.
>> >>>>>>>When I step through the debugger, it looks like
>> >>>>>>>ValuesManager.valuesImpl
>> >>>>>>>is
>> >>>>>>>returning null.
>> >>>>>>>
>> >>>>>>>Alex/Peter, can one of you please take a look?
>> >>>>>>>
>> >>>>>>>Thanks,
>> >>>>>>>Om
>> >>>>>>>
>> >>>>>>>[1]
>>
>>>>>>>>>https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTes
>>>>>>>>>t
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> >
>>
>>
Re: [FlexJS] StatesTest example app broken?
Posted by OmPrakash Muppirala <bi...@gmail.com>.
I fixed this for myself by doing this:
In the FlexJS debug and release build external tool's arguments:
Change:
-output="${project_loc}\bin-debug\${project_name}.swf"
to:
-output="${project_loc}\bin-debug\${project_name}_flexjs.swf"
Then, for each FlexJS project, we need to change index.template's params
settings:
change:
"${swf}.swf", "flashContent",
to:
"${swf}_flexjs.swf", "flashContent",
Now, when we run FB's debug option, project_name.swf gets created by mxmlc
but we will be running project_name_flexjs.swf which was compiled by
falcon. This should let us debug the app as usual.
Thanks,
Om
On Fri, Sep 20, 2013 at 10:48 AM, Peter Ent <pe...@adobe.com> wrote:
> With a little direction from Alex, I'm able to run the app too. Here's
> what happened to me:
>
> I created a new Flex project and then imported the code from
> DataBindingTest. I deleted the default application Flash Builder created
> and I then changed the project's properties and made DataBindingTest.mxml
> an Application and made it the default application.
>
> Cannot do that. Flash Builder still uses mxmlc to compile that.
>
> To fix this, I renamed DataBindingTest.mxml to my project's original
> default application name, selected it and built it with the FlexJS
> external tool and now it works correctly.
>
> --peter
>
> On 9/19/13 3:04 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
> >I stepped through my working copy of DataBindingTest.
> >
> >The initHandler in Application.as gets called first, and sets up the
> >ValueManager. Then, the MyInitialView gets addedToParent, which fires off
> >the MXMLDataIntepreter which assigns the states.
> >
> >Which made me look at the call stack and again, there is the dreaded
> >XXX_c() which means that Falcon did not compile the SWF, MXMLC did.
> >
> >-Alex
> >
> >On 9/19/13 10:58 AM, "Peter Ent" <pe...@adobe.com> wrote:
> >
> >>As far as I can tell, this is what is happening:
> >>
> >>"states" is a property of ViewBase and the property is being set very
> >>quickly upon application load. The states setter function is assuming
> >>there is a valuesImpl loaded into the ValuesManager, but that's not the
> >>case because the Application's initHandler hasn't been called yet and it
> >>is there that valuesImpl is set in the ValuesManager.
> >>
> >>Not sure yet how to deal with this, but I will work on it.
> >>
> >>--peter
> >>
> >>On 9/19/13 12:09 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >>
> >>>I'll let you do the digging, but make sure the capitalization is right,
> >>>and that it is using the same ValuesImpl as DataBindingTest.
> >>>
> >>>On 9/19/13 9:02 AM, "Peter Ent" <pe...@adobe.com> wrote:
> >>>
> >>>>I'm not making any headway on this. There is a global style declaration
> >>>>which should associate a state implementation with any class:
> >>>>
> >>>>global
> >>>>{
> >>>> iStatesImpl:
> >>>>ClassReference("org.apache.flex.core.SimpleStatesImpl");
> >>>>}
> >>>>
> >>>>
> >>>>I don't know why this isn't being picked up. I'm going to try
> >>>>DataBindingTest and see how that goes.
> >>>>--peter
> >>>>
> >>>>On 9/19/13 11:12 AM, "Peter Ent" <pe...@adobe.com> wrote:
> >>>>
> >>>>>I am looking into this.
> >>>>>--peter
> >>>>>
> >>>>>On 9/19/13 1:03 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >>>>>
> >>>>>>I haven't tried StatesTest in a while. Can you work with
> >>>>>>DataBindingTest
> >>>>>>instead? It should have everything StatesTest has and more.
> >>>>>>
> >>>>>>-Alex
> >>>>>>
> >>>>>>On 9/18/13 9:58 PM, "OmPrakash Muppirala" <bi...@gmail.com>
> >>>>>>wrote:
> >>>>>>
> >>>>>>>I picked this project up [1] after a while and when I run the app, I
> >>>>>>>am
> >>>>>>>getting this RTE:
> >>>>>>>
> >>>>>>>TypeError: Error #1009: Cannot access a property or method of a null
> >>>>>>>object
> >>>>>>>reference.
> >>>>>>> at org.apache.flex.core::ViewBase/set
> >>>>>>>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\as
> >>>>>>>\
> >>>>>>>s
> >>>>>>>r
> >>>>>>>c
> >>>>>>>\
> >>>>>>>o
> >>>>>>>rg\apache\flex\core\ViewBase.as:83]
> >>>>>>> at
> >>>>>>>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\exampl
> >>>>>>>e
> >>>>>>>s
> >>>>>>>\
> >>>>>>>S
> >>>>>>>t
> >>>>>>>a
> >>>>>>>tesTest\src\MyInitialView.mxml:23]
> >>>>>>> at StatesTest/_StatesTest_MyInitialView1_c()
> >>>>>>> at
> >>>>>>>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\
> >>>>>>>S
> >>>>>>>t
> >>>>>>>a
> >>>>>>>t
> >>>>>>>e
> >>>>>>>s
> >>>>>>>Test\src\StatesTest.mxml:26]
> >>>>>>>
> >>>>>>>I resynced recently and I am guessing some recent changes break this
> >>>>>>>app.
> >>>>>>>When I step through the debugger, it looks like
> >>>>>>>ValuesManager.valuesImpl
> >>>>>>>is
> >>>>>>>returning null.
> >>>>>>>
> >>>>>>>Alex/Peter, can one of you please take a look?
> >>>>>>>
> >>>>>>>Thanks,
> >>>>>>>Om
> >>>>>>>
> >>>>>>>[1]
> >>>>>>>https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTest
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
>
>
Re: [FlexJS] StatesTest example app broken?
Posted by Peter Ent <pe...@adobe.com>.
With a little direction from Alex, I'm able to run the app too. Here's
what happened to me:
I created a new Flex project and then imported the code from
DataBindingTest. I deleted the default application Flash Builder created
and I then changed the project's properties and made DataBindingTest.mxml
an Application and made it the default application.
Cannot do that. Flash Builder still uses mxmlc to compile that.
To fix this, I renamed DataBindingTest.mxml to my project's original
default application name, selected it and built it with the FlexJS
external tool and now it works correctly.
--peter
On 9/19/13 3:04 PM, "Alex Harui" <ah...@adobe.com> wrote:
>I stepped through my working copy of DataBindingTest.
>
>The initHandler in Application.as gets called first, and sets up the
>ValueManager. Then, the MyInitialView gets addedToParent, which fires off
>the MXMLDataIntepreter which assigns the states.
>
>Which made me look at the call stack and again, there is the dreaded
>XXX_c() which means that Falcon did not compile the SWF, MXMLC did.
>
>-Alex
>
>On 9/19/13 10:58 AM, "Peter Ent" <pe...@adobe.com> wrote:
>
>>As far as I can tell, this is what is happening:
>>
>>"states" is a property of ViewBase and the property is being set very
>>quickly upon application load. The states setter function is assuming
>>there is a valuesImpl loaded into the ValuesManager, but that's not the
>>case because the Application's initHandler hasn't been called yet and it
>>is there that valuesImpl is set in the ValuesManager.
>>
>>Not sure yet how to deal with this, but I will work on it.
>>
>>--peter
>>
>>On 9/19/13 12:09 PM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>>>I'll let you do the digging, but make sure the capitalization is right,
>>>and that it is using the same ValuesImpl as DataBindingTest.
>>>
>>>On 9/19/13 9:02 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>>
>>>>I'm not making any headway on this. There is a global style declaration
>>>>which should associate a state implementation with any class:
>>>>
>>>>global
>>>>{
>>>> iStatesImpl:
>>>>ClassReference("org.apache.flex.core.SimpleStatesImpl");
>>>>}
>>>>
>>>>
>>>>I don't know why this isn't being picked up. I'm going to try
>>>>DataBindingTest and see how that goes.
>>>>--peter
>>>>
>>>>On 9/19/13 11:12 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>>>
>>>>>I am looking into this.
>>>>>--peter
>>>>>
>>>>>On 9/19/13 1:03 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>>>
>>>>>>I haven't tried StatesTest in a while. Can you work with
>>>>>>DataBindingTest
>>>>>>instead? It should have everything StatesTest has and more.
>>>>>>
>>>>>>-Alex
>>>>>>
>>>>>>On 9/18/13 9:58 PM, "OmPrakash Muppirala" <bi...@gmail.com>
>>>>>>wrote:
>>>>>>
>>>>>>>I picked this project up [1] after a while and when I run the app, I
>>>>>>>am
>>>>>>>getting this RTE:
>>>>>>>
>>>>>>>TypeError: Error #1009: Cannot access a property or method of a null
>>>>>>>object
>>>>>>>reference.
>>>>>>> at org.apache.flex.core::ViewBase/set
>>>>>>>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\as
>>>>>>>\
>>>>>>>s
>>>>>>>r
>>>>>>>c
>>>>>>>\
>>>>>>>o
>>>>>>>rg\apache\flex\core\ViewBase.as:83]
>>>>>>> at
>>>>>>>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\exampl
>>>>>>>e
>>>>>>>s
>>>>>>>\
>>>>>>>S
>>>>>>>t
>>>>>>>a
>>>>>>>tesTest\src\MyInitialView.mxml:23]
>>>>>>> at StatesTest/_StatesTest_MyInitialView1_c()
>>>>>>> at
>>>>>>>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\
>>>>>>>S
>>>>>>>t
>>>>>>>a
>>>>>>>t
>>>>>>>e
>>>>>>>s
>>>>>>>Test\src\StatesTest.mxml:26]
>>>>>>>
>>>>>>>I resynced recently and I am guessing some recent changes break this
>>>>>>>app.
>>>>>>>When I step through the debugger, it looks like
>>>>>>>ValuesManager.valuesImpl
>>>>>>>is
>>>>>>>returning null.
>>>>>>>
>>>>>>>Alex/Peter, can one of you please take a look?
>>>>>>>
>>>>>>>Thanks,
>>>>>>>Om
>>>>>>>
>>>>>>>[1]
>>>>>>>https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTest
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: [FlexJS] StatesTest example app broken?
Posted by Alex Harui <ah...@adobe.com>.
I stepped through my working copy of DataBindingTest.
The initHandler in Application.as gets called first, and sets up the
ValueManager. Then, the MyInitialView gets addedToParent, which fires off
the MXMLDataIntepreter which assigns the states.
Which made me look at the call stack and again, there is the dreaded
XXX_c() which means that Falcon did not compile the SWF, MXMLC did.
-Alex
On 9/19/13 10:58 AM, "Peter Ent" <pe...@adobe.com> wrote:
>As far as I can tell, this is what is happening:
>
>"states" is a property of ViewBase and the property is being set very
>quickly upon application load. The states setter function is assuming
>there is a valuesImpl loaded into the ValuesManager, but that's not the
>case because the Application's initHandler hasn't been called yet and it
>is there that valuesImpl is set in the ValuesManager.
>
>Not sure yet how to deal with this, but I will work on it.
>
>--peter
>
>On 9/19/13 12:09 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
>>I'll let you do the digging, but make sure the capitalization is right,
>>and that it is using the same ValuesImpl as DataBindingTest.
>>
>>On 9/19/13 9:02 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>
>>>I'm not making any headway on this. There is a global style declaration
>>>which should associate a state implementation with any class:
>>>
>>>global
>>>{
>>> iStatesImpl:
>>>ClassReference("org.apache.flex.core.SimpleStatesImpl");
>>>}
>>>
>>>
>>>I don't know why this isn't being picked up. I'm going to try
>>>DataBindingTest and see how that goes.
>>>--peter
>>>
>>>On 9/19/13 11:12 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>>
>>>>I am looking into this.
>>>>--peter
>>>>
>>>>On 9/19/13 1:03 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>>
>>>>>I haven't tried StatesTest in a while. Can you work with
>>>>>DataBindingTest
>>>>>instead? It should have everything StatesTest has and more.
>>>>>
>>>>>-Alex
>>>>>
>>>>>On 9/18/13 9:58 PM, "OmPrakash Muppirala" <bi...@gmail.com>
>>>>>wrote:
>>>>>
>>>>>>I picked this project up [1] after a while and when I run the app, I
>>>>>>am
>>>>>>getting this RTE:
>>>>>>
>>>>>>TypeError: Error #1009: Cannot access a property or method of a null
>>>>>>object
>>>>>>reference.
>>>>>> at org.apache.flex.core::ViewBase/set
>>>>>>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\as\
>>>>>>s
>>>>>>r
>>>>>>c
>>>>>>\
>>>>>>o
>>>>>>rg\apache\flex\core\ViewBase.as:83]
>>>>>> at
>>>>>>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\example
>>>>>>s
>>>>>>\
>>>>>>S
>>>>>>t
>>>>>>a
>>>>>>tesTest\src\MyInitialView.mxml:23]
>>>>>> at StatesTest/_StatesTest_MyInitialView1_c()
>>>>>> at
>>>>>>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\S
>>>>>>t
>>>>>>a
>>>>>>t
>>>>>>e
>>>>>>s
>>>>>>Test\src\StatesTest.mxml:26]
>>>>>>
>>>>>>I resynced recently and I am guessing some recent changes break this
>>>>>>app.
>>>>>>When I step through the debugger, it looks like
>>>>>>ValuesManager.valuesImpl
>>>>>>is
>>>>>>returning null.
>>>>>>
>>>>>>Alex/Peter, can one of you please take a look?
>>>>>>
>>>>>>Thanks,
>>>>>>Om
>>>>>>
>>>>>>[1]
>>>>>>https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTest
>>>>>
>>>>
>>>
>>
>
Re: [FlexJS] StatesTest example app broken?
Posted by Peter Ent <pe...@adobe.com>.
As far as I can tell, this is what is happening:
"states" is a property of ViewBase and the property is being set very
quickly upon application load. The states setter function is assuming
there is a valuesImpl loaded into the ValuesManager, but that's not the
case because the Application's initHandler hasn't been called yet and it
is there that valuesImpl is set in the ValuesManager.
Not sure yet how to deal with this, but I will work on it.
--peter
On 9/19/13 12:09 PM, "Alex Harui" <ah...@adobe.com> wrote:
>I'll let you do the digging, but make sure the capitalization is right,
>and that it is using the same ValuesImpl as DataBindingTest.
>
>On 9/19/13 9:02 AM, "Peter Ent" <pe...@adobe.com> wrote:
>
>>I'm not making any headway on this. There is a global style declaration
>>which should associate a state implementation with any class:
>>
>>global
>>{
>> iStatesImpl: ClassReference("org.apache.flex.core.SimpleStatesImpl");
>>}
>>
>>
>>I don't know why this isn't being picked up. I'm going to try
>>DataBindingTest and see how that goes.
>>--peter
>>
>>On 9/19/13 11:12 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>
>>>I am looking into this.
>>>--peter
>>>
>>>On 9/19/13 1:03 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>
>>>>I haven't tried StatesTest in a while. Can you work with
>>>>DataBindingTest
>>>>instead? It should have everything StatesTest has and more.
>>>>
>>>>-Alex
>>>>
>>>>On 9/18/13 9:58 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>>>
>>>>>I picked this project up [1] after a while and when I run the app, I
>>>>>am
>>>>>getting this RTE:
>>>>>
>>>>>TypeError: Error #1009: Cannot access a property or method of a null
>>>>>object
>>>>>reference.
>>>>> at org.apache.flex.core::ViewBase/set
>>>>>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\as\s
>>>>>r
>>>>>c
>>>>>\
>>>>>o
>>>>>rg\apache\flex\core\ViewBase.as:83]
>>>>> at
>>>>>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples
>>>>>\
>>>>>S
>>>>>t
>>>>>a
>>>>>tesTest\src\MyInitialView.mxml:23]
>>>>> at StatesTest/_StatesTest_MyInitialView1_c()
>>>>> at
>>>>>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\St
>>>>>a
>>>>>t
>>>>>e
>>>>>s
>>>>>Test\src\StatesTest.mxml:26]
>>>>>
>>>>>I resynced recently and I am guessing some recent changes break this
>>>>>app.
>>>>>When I step through the debugger, it looks like
>>>>>ValuesManager.valuesImpl
>>>>>is
>>>>>returning null.
>>>>>
>>>>>Alex/Peter, can one of you please take a look?
>>>>>
>>>>>Thanks,
>>>>>Om
>>>>>
>>>>>[1]
>>>>>https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTest
>>>>
>>>
>>
>
Re: [FlexJS] StatesTest example app broken?
Posted by Alex Harui <ah...@adobe.com>.
I'll let you do the digging, but make sure the capitalization is right,
and that it is using the same ValuesImpl as DataBindingTest.
On 9/19/13 9:02 AM, "Peter Ent" <pe...@adobe.com> wrote:
>I'm not making any headway on this. There is a global style declaration
>which should associate a state implementation with any class:
>
>global
>{
> iStatesImpl: ClassReference("org.apache.flex.core.SimpleStatesImpl");
>}
>
>
>I don't know why this isn't being picked up. I'm going to try
>DataBindingTest and see how that goes.
>--peter
>
>On 9/19/13 11:12 AM, "Peter Ent" <pe...@adobe.com> wrote:
>
>>I am looking into this.
>>--peter
>>
>>On 9/19/13 1:03 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>>>I haven't tried StatesTest in a while. Can you work with
>>>DataBindingTest
>>>instead? It should have everything StatesTest has and more.
>>>
>>>-Alex
>>>
>>>On 9/18/13 9:58 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>>
>>>>I picked this project up [1] after a while and when I run the app, I am
>>>>getting this RTE:
>>>>
>>>>TypeError: Error #1009: Cannot access a property or method of a null
>>>>object
>>>>reference.
>>>> at org.apache.flex.core::ViewBase/set
>>>>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\as\sr
>>>>c
>>>>\
>>>>o
>>>>rg\apache\flex\core\ViewBase.as:83]
>>>> at
>>>>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\
>>>>S
>>>>t
>>>>a
>>>>tesTest\src\MyInitialView.mxml:23]
>>>> at StatesTest/_StatesTest_MyInitialView1_c()
>>>> at
>>>>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\Sta
>>>>t
>>>>e
>>>>s
>>>>Test\src\StatesTest.mxml:26]
>>>>
>>>>I resynced recently and I am guessing some recent changes break this
>>>>app.
>>>>When I step through the debugger, it looks like
>>>>ValuesManager.valuesImpl
>>>>is
>>>>returning null.
>>>>
>>>>Alex/Peter, can one of you please take a look?
>>>>
>>>>Thanks,
>>>>Om
>>>>
>>>>[1] https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTest
>>>
>>
>
Re: [FlexJS] StatesTest example app broken?
Posted by Peter Ent <pe...@adobe.com>.
I'm not making any headway on this. There is a global style declaration
which should associate a state implementation with any class:
global
{
iStatesImpl: ClassReference("org.apache.flex.core.SimpleStatesImpl");
}
I don't know why this isn't being picked up. I'm going to try
DataBindingTest and see how that goes.
--peter
On 9/19/13 11:12 AM, "Peter Ent" <pe...@adobe.com> wrote:
>I am looking into this.
>--peter
>
>On 9/19/13 1:03 AM, "Alex Harui" <ah...@adobe.com> wrote:
>
>>I haven't tried StatesTest in a while. Can you work with DataBindingTest
>>instead? It should have everything StatesTest has and more.
>>
>>-Alex
>>
>>On 9/18/13 9:58 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>
>>>I picked this project up [1] after a while and when I run the app, I am
>>>getting this RTE:
>>>
>>>TypeError: Error #1009: Cannot access a property or method of a null
>>>object
>>>reference.
>>> at org.apache.flex.core::ViewBase/set
>>>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\as\src
>>>\
>>>o
>>>rg\apache\flex\core\ViewBase.as:83]
>>> at
>>>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\S
>>>t
>>>a
>>>tesTest\src\MyInitialView.mxml:23]
>>> at StatesTest/_StatesTest_MyInitialView1_c()
>>> at
>>>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\Stat
>>>e
>>>s
>>>Test\src\StatesTest.mxml:26]
>>>
>>>I resynced recently and I am guessing some recent changes break this
>>>app.
>>>When I step through the debugger, it looks like ValuesManager.valuesImpl
>>>is
>>>returning null.
>>>
>>>Alex/Peter, can one of you please take a look?
>>>
>>>Thanks,
>>>Om
>>>
>>>[1] https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTest
>>
>
Re: [FlexJS] StatesTest example app broken?
Posted by Peter Ent <pe...@adobe.com>.
I am looking into this.
--peter
On 9/19/13 1:03 AM, "Alex Harui" <ah...@adobe.com> wrote:
>I haven't tried StatesTest in a while. Can you work with DataBindingTest
>instead? It should have everything StatesTest has and more.
>
>-Alex
>
>On 9/18/13 9:58 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
>>I picked this project up [1] after a while and when I run the app, I am
>>getting this RTE:
>>
>>TypeError: Error #1009: Cannot access a property or method of a null
>>object
>>reference.
>> at org.apache.flex.core::ViewBase/set
>>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\as\src\
>>o
>>rg\apache\flex\core\ViewBase.as:83]
>> at
>>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\St
>>a
>>tesTest\src\MyInitialView.mxml:23]
>> at StatesTest/_StatesTest_MyInitialView1_c()
>> at
>>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\State
>>s
>>Test\src\StatesTest.mxml:26]
>>
>>I resynced recently and I am guessing some recent changes break this app.
>>When I step through the debugger, it looks like ValuesManager.valuesImpl
>>is
>>returning null.
>>
>>Alex/Peter, can one of you please take a look?
>>
>>Thanks,
>>Om
>>
>>[1] https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTest
>
Re: [FlexJS] StatesTest example app broken?
Posted by Alex Harui <ah...@adobe.com>.
I haven't tried StatesTest in a while. Can you work with DataBindingTest
instead? It should have everything StatesTest has and more.
-Alex
On 9/18/13 9:58 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>I picked this project up [1] after a while and when I run the app, I am
>getting this RTE:
>
>TypeError: Error #1009: Cannot access a property or method of a null
>object
>reference.
> at org.apache.flex.core::ViewBase/set
>states()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\frameworks\as\src\o
>rg\apache\flex\core\ViewBase.as:83]
> at
>MyInitialView()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\Sta
>tesTest\src\MyInitialView.mxml:23]
> at StatesTest/_StatesTest_MyInitialView1_c()
> at
>StatesTest()[C:\p\flex_os\workspace\flexroot\git\flex-asjs\examples\States
>Test\src\StatesTest.mxml:26]
>
>I resynced recently and I am guessing some recent changes break this app.
>When I step through the debugger, it looks like ValuesManager.valuesImpl
>is
>returning null.
>
>Alex/Peter, can one of you please take a look?
>
>Thanks,
>Om
>
>[1] https://fisheye6.atlassian.com/browse/flex-asjs/examples/StatesTest