Andrew, thanks for the info.
Editing the XML is not for me, I'm not into code.
Nor am I 'into code'. Whilst it's not quite 'rocket science', to my mind if you have to delve into the XML it kind of misses the point of having a GUI front-end/XML generator for krpano.
It has always been my understanding that the key purpose/goal of APT is to enable people to produce virtual tours for the krpano panorama viewer without having to understand the XML stuff.
APT is 'the new kid on the block' and still very much in development, but if it remains the case that rather basic functionality, such as the features you seek, (which AFAIK can be set via the Pano2VR and Flashificator GUIs for Pano2VR and Flash Panorama Player respectively) can only be obtained by editing the XML then I would have to conclude that APT has failed to meet the developers' declared goals.
I am disappointed when it seems that every rather basic feature request is met with the response 'you can always hand edit the XML'. I can accept that given the exceptional depth of functionality offered by krpano, and the rate at which new features are added, that not every feature and capability can be made available via the APT GUI but I do feel that APT should at least match the most commonly used basic capabilities/features of established competitors if it is to be an acceptable alternative.
There's no doubting that APT is easy to use, but IMO it just doesn't yet do enough and I feel as if I'm too often having to make excuses for its current shortcomings when responding to posts on this and other forums.
You may like to make a request for the addition of the features you seek in the APT GUI - they are desirable and 'sensible' features that many others would like to see made available in APT: http://www.autopano.net/forum/f24-the-future
I find the inability to set viewing limits the most frustrating inadequacy of APT currently.
That's my rant for the day........