This content has been marked as final. Show 6 replies
Are you using Flex Builder2? if so, go to Project, Properties, Build Path, and add the view folder. Then take the view. out of the popup line.
I am fairly new to Flex 2 myself, and am particularly soft on application structure strategy.
Thanks Tracy !
That did the trick ... It was more of a FlexBuilder issue then ...
I wonder though if there's a way to have the path as part of the code. It should. When a custom mxml file is included in a main file and referenced through a namespace declared in the main container tag (eg. xmlns:MyComp="view.*"), the path to the file is in the code, not as an IDE project's setting ... What if I was not using FlexBuilder ?
Thanks again, JF
try import view.myPopUpComponent at the top of your script.
better yet, if you're using flexBuilder, when typing your
Press Ctrl-Space and it should offer you the completion of myPopUpComponent - if you accept it (press Enter), it'll automatically add the import statement for you.
Thanks Tim ! That works too ... I should've thought of it ... that's the way to go ...
The Build Path feature of FlexBuilder must be intended for reusable custom packages located outside of your project's file structure.
You're welcome - by the way by convention, Classes (and hence MXML components) are usually named with initial caps, and instances with initial lower case. Obviously the compiler doesn't care, but if other people are reading your code it's clearer when you follow that convention. So in your example that would be view.MyPopUpComponent.