Sorry to cram all this in to a single post with a vague title. I'm too pressed for time to do it in a more orderly fashion.
1. Don't rebuild the multi-resolution image files unless necessary. Panotour is smart enough to keep track of this and not rebuild the images while it is open, but if I close the project and reopen it, it insists on rebuilding all the images. Maybe it should keep track of the date/time it last built the images and if the files on disk match that date/time, don't touch them. (if there is a need to force a rebuild, the option to delete before building is already available.)
2. It should remember where I last built the project. I shouldn't have to re-select the build location every time I reopen a project file.
3. Have a place in the template to modify the mainloadpano action, so that I can run some logic at startup. I am using this to add a button to enable/disable the gyroscope, and I need to check if the device actually has a gyro before I make the button visible. Also, I want to be able to set the "KEEPVIEW" option.
4. The ability to create hotspots that include lookat coordinates. krpano supports this, and the interface seems to allow setting the initial view for a hotspot link, but it doesn't seem to do anything. I have one that I modified the xml by hand to do what I wanted. I can send it to you if you want to see it.
5. Ability to have the panotour maps start at a default location of the user choosing. Maybe even use something like Google's location services to automatically get in the general vicinity? Having to pan to the other side of the globe before I can drop a pin on the map is a bit tedious. (I'm needing to drop pins where no address exists to search for)
Thanks for your feedback. Some of your requested features will surely be part of a future version of Panotour.
The following are already in Panotour :
1. Don't rebuild the multi-resolution image files unless necessary. When you re-open a project, we do not parse the already created files, and as we do not keep a trace of the previous project state, we do not know if we have to create the tiles. That's true. So if you re-open a project to add a single panorama, we will re-create all the tiles of all your panoramas . But if you re-open the panorama to add spots, or plugins, etc..., then you can choose "Export pictures/Never" in the Tour Build tab. http://www.autopano.net/wiki-en/action/ … Tour_Build
4. The ability to create hotspots that include lookat coordinates.
When you set the "default view" of a spot, you set the lookat coordinates of the spot. But you have to select a transition in the Transition field below the linked panorama in the Hotspot properties tab, to go load the new panorama to these coordinates (or to move the current one). http://www.autopano.net/wiki-en/action/ … ies_-_Link
1. the reason I want this is because I'm adding photos to tours over time, and I'm using rsync to upload the tour to my web server. Ideally, it would leave the images alone for parts of the tour that have not changed, so that they wouldn't need to be re-uploaded constantly.
4. thanks! setting the transition was the step I was missing. With that set, it works just like I expected it to. It seems like it might be more intuitive to automatically set the transition to "Load Spot View" when a default hotspot view is set.
7. Just ran into another feature I would like to have. export of equirectangular images after importing cube faces. I needed to patch the nadir, so I exported cube faces, edited the down face, and wanted to re-save it as an equirectangular image that I can easily store. I ended up using krpanotools to do what I wanted, but it would have been nice to do it all from within panotour. (thanks for the license export button though!)
Actually, I would rather see the ability to export a single face, and reimport it into AutoPano so that I could have fixed it before the equirectangular image was ever created. (or just more robust nadir handling in autopano)