Well, this goes into the category of 'Where does Flex create the project
files?' quirks:
Quick answer: The debugger was pointing to a location where Flex
essentially wasn't building the latest compiles.
Long answer: If you ever run into really strange issues where you are
convinced that it should be working, but ti doesn't, check that the
build path and the output folder URL point to the same location.
Explanation:
I'm running Flex on a Mac, but am working on a .NET based server end
solution, so I have to essentially build the Flex app against the IIS
server location on a network Win2003 drive.
Problem with the Mac is that it doesn't play well with the Windows
network (at least so far), so it always looses the shared drives when I
put it to sleep. Waking it up and reconnecting the networked shares
messes up Flex when the shared name all of a sudden changes (because the
Mac assigns a different name to it dynamically).
So, all this to say that creationPolicy works as expected and this is
something external to Flex, but still the source of some frustration if
you don't pay attention to it.
Hope this helps someone else! :-)
Jurgen
Jurgen Beck wrote:
I'm running into a strange problem with the Accordion container. Setting
creationPolicy to 'all' on the Accordion container will not force the
controls in all the views to be created. It behaves as if it is still
set to the default (auto).
Anyone run into the same problem?
Jurgen
