People at Easypano are always working for the needs of our customers. We've noticed that many of you are talking about the cache of viewed images, which will enable you to have a faster review of them.
As we all know that tours created by Tourweaver 3.00 are unable to cache the viewed iamges, and we haven't added this feature to Tourweaver 4.00 due to the considerations of its working mechanism and the cache capacity of Explorers.
In Tourweaver 4.00, we have adopted the feature of Slice Display and two sets of images(for normal view and full screen view respectively), both of which will accelerate the image download, but in either case, more images will be generated in the tour file, resulting larger file size(complained by some). Once the cache feature is adopted, all these images will be stored in Explorers, in result of which Explorer will eat up much more physical memory of computer and slow performance of your computer will occur, even crash, but unfortunately, we cant help in improving the performance of Explorers, for this can be counted on their own developers.
Furthermore, how you want the tour to cache the viewed images is another problem that should be taken into account. One is that when the tour is switched between normal view and full screen view (Not recommend caching full screen images for their sizes). The other is to cache the previous scene after you jump to another one (For normal view). Which one do you prefer? Actually, we dont recommend both of them.
In any cases, it is your choice about what features you would like to have with the program, and we will listen to most of you, but sorry for those asking for special needs(However, we can customize the program for certain customers to meet their own needs).
Please do not hesitate to leave thoughts here, and all of them will be highly appreciated.
BTW, the feature of preloading will be added in next update together with the fixing of other minor bugs by the end of this month if everything goes well.
Easypano Holdings Inc.