|
All, I
am using the loader to load a workspace area within my app with other “child”
applications. I found from the list about implementing the following
functions in my “child” applications. function getPreferredHeight() {
return _parent.layoutHeight; } function
getPreferredWidth() {
return _parent.layoutWidth; } Doing that seemed to solve a ton of weird issues I was
having. I now just have two issues, one minor and the other one more of a
pain. The first on that is no big deal, but the flex progress bar doesn’t
seem to show up. Or if it does it is right at the end and just flashes up
really quick. Is there anything that could be preventing this from showing?
For example if this was the first time the mxml file was being accessed,
the server will have to compile it. This will take a couple of seconds,
the whole time the app just seems to be hung, where I was thinking the status
bar would be up. Second item is that it seems like the first time I load a
child application in the loader all the initialize stuff happens but not the second
time. So the steps are that a user clicks and item, I load an
application. The user clicks a different item, I re-use that loader to
load a new item. If the user goes back to the first item a lot of the
events act weird, it doesn’t go through the initialize etc. I
thought I read somewhere that you have to “unload” the item before
loading something else into the loader, but I can’t seem to find anything
on that. Any help would be appreciated. Thanks Jeff Yahoo! Groups Links
|
