fieldOfView | SPi-V devSPi-V 1.4 beta 2
Submitted by Aldo on March 22, 2007 - 18:03.
Changelog:
- 'gradient' layers
- limit number of loops for ramp
same syntax as loop parameter for sound - 'ready' event for panogroup and uigroup
fires when all elements in the group are ready - added 'persistent' option to getProperty/setProperty
gets/sets values to internal xml document, so changes persist when moving between scenes. - numerous fixes for the new downloader
- fixed 'resize-flash' in LDM
minor alteration of SPi-V init behavior required - 'hotspots' no longer block navigation
- fixed potential memory leak changing scenes and loading new tours
Re: SPi-V 1.4 beta 2
Just 2 things that I noticed when playing panoramas (in movie created in Director).
1) Arrows on the map does not disappear when I go to another panorama - screen shot will be sent to you
2) I see a Spi-V information for less than second at the beginning.
My tour has licensed xml file.... I can only read message: Licensed to: .....
Is is possible to add small images in this forum (not to send e-mails to you or give links)?
I don't understand most of changelogs in new Spi-V. Maybe please attach a link to forum where this problem was mentioned or write (NEW or sth).
Karol
Re: SPi-V 1.4 beta 2
Unfortunately, the screenshot you send me doesn't tell me much. What is supposed to happen? Are you moving the arrow uielement around, or are you changing the "visible" property of multiple elements? Does the problem also exhibit in SPi-V 1.3?
I'll look in to the second problem.
There is no easy way to upload images in comments. Links work fine though...
I have added some links to the changelog
problem found
The first problem you outlined is also visible with the hirshhorn tour:
http://fieldofview.com/spv/show14.php?file=hirshhorn.xml
The hotspots in the map stay in their 'compass' state.
Will fix it in the next beta.
FIXED
(beta 3)
SPi-V 1.4 beta 2 needs a diet
Due to the new version control system I am using for SPi-V 1.4, the betas may display a bit of 'yo-yo-ing'. The current beta has about 50 Kb of unused data/debug code in it. The final release will ofcourse be as lean as possible.