Hi, as i use swfaddress to deep link - allowing direct links to specific panoramas in a tour - i need a consistent system of pano ids as i use these ids to identify the panorama that is requested. I noticed, that whenever i delete a pano in panotour pro, the panos get reindexed. If the panoramas are reindexed, then i need to update all the links pointing to that specific panorama. it would be useful to have a feature implemented, where you can chose if you want reindexed panoramas or not. In the GUI it could be implemented at the Project properties with a check box. This could then effect how the reindexing works: A: without reindexing -> when a pano is deleted, that id is not used anymore B: with reindexing -> when a pano is deleted, the whole tour is reindexed.
any ideas if i can expect this in a future version
I also have a problem with the reindexing, but for a different reason. I add new panos from the same location to a tour over time, and I always want the newest to come up first. Every time I add a pano and make it the first to display, all the others are reindexed, and output again. this is quite annoying because it means that I either have to change the filenames manually or reupload the entire tour. I would rather see the panos in a tour have user definable names/identifiers that are saved in the panotour file. It would be fine if the default name is chosen using the current indexing method, but once a name is chosen for a given pano it should not change unless I explicitly request a change.
@Jeremiah i noticed that if you change the order of the thumbnails eg. in the thumbnail stack, then you also change the IDs of the images in the system. In the first moment this seems to come in handy, but it's obviously a big mistake in panotour pro. Why? - One could wish to have a thumbnail stack AND a panorama list at the same time, showing different panoramas. This is impossible with the current system. you cannot decide if you want to have a panorama included in the thumbnail stack or not. - If you delete a panorama, then the resulting gap will be closed. This is very bad because the IDs are not consistent anymore - The IDs of the Panoramas MUST be independent from other numeration systems like the panorama list or thumbnail stack.