Hi Paul,
Unfortunately, the preload resources action is limited to hard coded paths. perhaps the use fo variables here could be added to the wishlist.
My understanding of resources, is that they load into memory when called unless added to one of the preloaded options. But as you are using images dynamically this is not possible.
I wonder then whether resources would remain in memory across pages. If this is the case, then you could load these resources on page one in a hidden or off page frame by using your setimage command once the variable has updated.
If this works, then the image would already be in memory when page two loads. However, this does seem unlikely as it would mean that Opus publications would simple eat up more and more memory as publications progressed.
Alternatively, I would suggest looking at the design of the publication as to what is loading that is causing such a long delay. For example, if these 30 image thumbnails are in fact simply the high editions resized using Opus, then consider producing thumbnails from the original files outside of Opus and using these in Opus and linking to the large images for you mouse over /clicks.
Mack
_________________ When you have explored all avenues of possibilities, what ever remains, how ever improbable, must be the answer.
Interactive Solutions for Business & Education Learn Anywhere. Learn Anytime.
www.interaktiv.co.uk +44 (0) 1395 548057
|