vr.window_width = windowW;
vr.window_height = windowH;
vr.window_x = refX;//BRS to move when the page furniture moves
vr.window_y = refY;//BRS to move when the page furniture moves
vr.autorotate = PanoNode.attributes.rotation;
vr.autorotate_delay = PanoNode.attributes.delay;
// change initial viewing parameters
vr.pan = PanoNode.attributes.panInit;
vr.tilt = PanoNode.attributes.tiltInit;
vr.fov = PanoNode.attributes.fovInit;
You can see from the last few that I use an xml file to set the parameters - and the hotspot locations - for each pano in each tour. Have a look at http://www.briansutton.net.
I started with Thomas' demo code, but I now have 700 lines (I'm not a very efficient coder and there are lots of comments to remind me at a later date what I did!)
I still have trouble getting the controller to show
- it's there but behind the black masking on the bottom left of the page somewhere. I was glad just to be able to get the panos the size and place I want...actually Thomas has just released version 6.5 to correct a small glitch I mentioned in the way the positioning and sizing works in v6 as compared with v5.I've also yet to work out how to use the new hotspotting in pano2qtvr
(used to be QuickTime only but I can't see how to reference a swf in the GUI) so I still set the hotspots in the ActionScript; something graphical would be easier than trila nd error to get them in the right place by trying the result each time I reset the pan and tilt for the hotspot/So we all have problems! Not only are small things easily missed, but also sometimes one can be shy to ask or even answer a question because people will think one silly
. Maybe someone can give me a hint on one or two of these questions!Best regards,
Brian
