Jan_T wrote:
Some questions:
- how proxies are used?
- how does the pano-to-pano-while-in-fullscreen-feature does work?
- how do i create point hotspots? (i tried to understand the example, but i didnt...)
The example I posted is maybe a bit too complicated to understand without explanations. A tutorial for it is on its way. In the meantime I will try to explain it with just words.
If you open the hotspot editor you now have a "point hotspot" tab. With a double click you can add point hotspots to the panorama. On top of the screen you can add the parameters like the ID (only useful if you use proxies), skin id (to have more then one hotspot symbol), title, url and target. The later 3 are the same as for area hotspots so if you want to create a simple tour just add the name of the next panorama into the field. If the file name ends with ".swf" Pano2VR assumes it is another panorama (works also for area hotspots!).
In the case of a new panorama this new pano is loaded internally and the images and parameters like hotspots are taken out and loaded into the original player. The skin of the new panorama will be ignored! If you are generating a tour only the first panorama needs a skin! The result is that for the browser sees still the same swf file and nothing has changed. Also a nice consequence is that this method avoids the problems discussed some time ago.
You can also design your own point hotspots within the skin editor. To do that you just need to add a "hotspot template" as parent and everything below that object in the tree is ignored in the normal skin but instead used as the point hotspot display object. You can use the hotpots title information with $hs, the url with $hu and the target with $ht in text fields and gotoURLs. You can address different templates with "ID" in the Skin and the "Skin ID" field in the point hotspot.
The proxy property brings back the hotspot events into the skin. Just use the hotspot ID (which is just the number for area hotspots). This avoids the need to generate a separate hotspot template for each hotspot to do trigger different skin based actions. The proxy receives the same events (currently only click, mouse enter and mouse leave) as the hotspot in the panorama so in the example a click on the point hotspot triggers the same event as a click on the dot within the map because the dot is a proxy for the point hotspots. For that reason there are no urls attached in the point hotspots and everything is manged in that point object. The result is that the "code" for moving the radar, url of the next pano, correcting north,... is only in the dot and not in each point hotspot.
I hope this long explanation makes at least a little sense to you. As said, tutorials will follow soon.
