Sie sind nicht angemeldet.

Lieber Besucher, herzlich willkommen bei: krpano.com Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.

1

Freitag, 11. Februar 2011, 12:14

2500 polygonal hotspots... Is it possible?

Hi!

I'll plan to make а virtual tour which will include 2500 polygonal hotspots.
* 16 360VR pano in VR tour
* VR pano resolution is 14000x7000px
- This part is already realized
* 100-250 polygonal hotspots per a VR pano, 2500 hotspots total
* 4-50 point per a hotspot
* Each of hotspots will open a pop-up window (textfild plugin)
- This part in plans only.

Are there any hidden obstacles or limitations?

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »Valentin« (11. Februar 2011, 14:40)


2

Freitag, 11. Februar 2011, 15:07

that will be alot of xml to read at the start. i would make an action that creates the polyspots onstart of each scene. that way the only ones that are actually in use at any given time are the ones in the current scene. i think that would be better than having them all created and using visible true/false to view them.

3

Montag, 14. Februar 2011, 12:53

Hi,

when the hotspots are defined inside the <scene> or inside the pano xml,
then only the hotspots of the current scene/pano will be shown/calculated/rendered of course,

there is no direct limitation, but the cpu needs a bit time for calculation and rendering a hotspot,
so more hotspots are also needing more cpu time of course,

in a normal case 100-250 polygonal hotspots shouldn't be a big problem on todays computers,
but I can't say to sure of course, the best way to find out would be to try it, e.g. try to draw a
lot of hotspots with the editor plugin and see how it behaves...

best regards,
Klaus

4

Dienstag, 15. Februar 2011, 18:53

Thank you very much!

5

Samstag, 19. Februar 2011, 23:36

One more question:
How make all hotspots visible after panorama loading?

I have tried some ways but have failed.

1. Create additional XML with hotspot and make loadxml actions

Quellcode

1
<events onloadcomplete="loadxml([hotspot.xml], null, KEEPALL);"/>

- The panorama picture is lost because <image> doesn't support keep attribute

2. To set visibility in style for all hotspots

Quellcode

1
<events onloadcomplete="set(style[hs].visible,true);"/>

- "set" and "style" are incompatible

3. Extensive way

Quellcode

1
2
3
4
5
<events onloadcomplete="set(hotspot[hs1].visible,true);
 	set(hotspot[hs2].visible,true);
 	set(hotspot[hs3].visible,true);
 	....
 	set(hotspot[hs2500].visible,true);"/>

- It works properly but code is very long

Сould you advice something?

6

Sonntag, 20. Februar 2011, 01:09

switch(hotspot.visible);

will toggle the entire hotspot layer on and off.

7

Sonntag, 20. Februar 2011, 20:12

It's really simple *smile* Thanks!

But this way requires double switching: true->false->true

Quellcode

1
2
3
<style name="hs" visible="true" ............./>
<events onxmlcomplete="switch(hotspot.visible);"
    	onloadcomplete="switch(hotspot.visible);"/> 


If to do only one switching false->true

Quellcode

1
2
<style name="hs" visible="false" ............./>
<events onloadcomplete="switch(hotspot.visible);"/> 


...it doesn't work

I don't understand this logic *unsure*