Could be a number of things, might be good to post the source code up so we can have a look at it At first glance it might be the fact that flex cannot find your component because you haven't given it the correct path The usual structure for declaring mxml component is to qualify them with a namespace so the compiler knows where to look. For example for standard flex component you prefix 'mx' to the front of the components tag: mx:label text='boo Remember mxml is a subset of xml so all the same rules apply. So I would first try adding a namespace declaration to your root tag and then qualifying your component with that namespace.
The namespace should point to the folder you have the components source file in i. E Application xmlns:customcomponents="myComponents Then qualify the component like so: customcomponents:MyComponent dataProvider="{dataProvider}" width="100%" height="100%" x="0" y="0" id="dc" verticalCenter="0" horizontalCenter="0 A handle tip is if you press control + spacebar and cannot find your component declare then flex cannot see your component, its the same with classes they have to be imported to be used, this is just a form of that Hope this helps Jon.
Could be a number of things, might be good to post the source code up so we can have a look at it. At first glance it might be the fact that flex cannot find your component because you haven't given it the correct path. The usual structure for declaring mxml component is to qualify them with a namespace so the compiler knows where to look.
For example for standard flex component you prefix 'mx' to the front of the components tag: Remember mxml is a subset of xml so all the same rules apply. So I would first try adding a namespace declaration to your root tag and then qualifying your component with that namespace. The namespace should point to the folder you have the components source file in i.e.
Then qualify the component like so: A handle tip is if you press control + spacebar and cannot find your component declare then flex cannot see your component, its the same with classes they have to be imported to be used, this is just a form of that. Hope this helps. Jon.
At first glance it might be the fact that flex cannot find your component because you haven't given it the correct path. The usual structure for declaring mxml component is to qualify them with a namespace so the compiler knows where to look. Remember mxml is a subset of xml so all the same rules apply.
So I would first try adding a namespace declaration to your root tag and then qualifying your component with that namespace. The namespace should point to the folder you have the components source file in i.e. A handle tip is if you press control + spacebar and cannot find your component declare then flex cannot see your component, its the same with classes they have to be imported to be used, this is just a form of that.
Hope this helps.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.