This content has been marked as final. Show 3 replies
Full or relative urls? Are you doing any navigatetoURLs?
Trace the image source values for a while, perhaps you will see something.
yes, all full urls.
What I do is:
- Image loading queue, to load only one image at a time (same issue if there is no queue)
- Added UPDATE and COMPLETE event handlers to each image. Result: paths are ok, no error or warning messages in the console, all these events are firect correctly.
What is really interesting:
The images that cannot be displayed are also not displayable viewed directly with the browser (by entering the image path), It then tells you about a broken image. When I save the image file, it is ok.
Once the browser is closed and restarted it works again for a while.
Here is the queue code that I am using (the image and source params are all correct, even when it comes to this issue):
I have to add something new I found out:
The flex app is loaded into a popup window (called by using <a href="..." target="_blank">).
When I now close that window with the flex app, I can access the image again, wich means it is not broken anymore oO
However, could it be that my Flex app doesnt close the image stream correctly or locks the image file in the cache somehow?