Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
better would be to use - keep="true" - for these plugins/hotspots that should be stay/kept when loading a other pano,
Quoted
From my understanding I think I could trim the XML quite a bit by removing just about all duplicate XML from the ones associated with the secondary rooms, etc. That is, as long as KEEPBASE, or KEEPALL is used and nothing else conflicts with those, ti's safe to reomove the buttons plugin, cusor, dispaly, textstyle, soundinterface, and ... from all but the first set of XML. The later sets will pretty much only contain the custom hotspots for than pano and the image type/tile settings.
![]() |
Source code |
1 |
<plugin ... keep="true" /> |
I personally use UltraEdit,
Quoted
And speaking of XML - a bit off topic but what XML editors do people use. I'm finding the XML support in Dreamweaver 8 is a bit lacking in that it' does not color code the bracketed conditionals so it can be a nightmare to find missing or extra brackets.
I do not think so
Quoted
I still need to know if theres a way to keep the hotspots active while the autotour is running
SAlut.the lookto/moveto/zoomto actions instead are 'blocking' actions,
they are changing the view, and while changing all other things are blocked (user input, actions execution)