FullScreen without any button, Yes We Can!...but
Posted: Sun Feb 21, 2010 10:03 pm
I've made a testpage with thumbnails that when clicked on open a Flash panorama directly in fullscreen mode.
Here's a link:
http://tinyurl.com/Direct-to-FullscreenPano
As such it is no problem to make this happen with a small Flash application as a helper, but like always there's some snakes in the grass.
Problem 1:
Letting that helper open a pano 'the normal way' takes forever, the (default) progress indicator in the skin seems to never end counting, and sometimes the pano doesn't load completely at all.
In short: this method of loading panos is to be avoided like the plague!
However, if I suppress visibility of the loading Pano and let my own progress bar in the helper do the counting, that very same pano loads like lightning!
Explanation? I have no idea!
Problem 2:
Pano2VR skin elements have a strange (= bad) effect on processor load.
A pano with one or two buttons doing absolutely nothing generates significant CPU usage, whereas the CPU shows no activity with a version of the same pano without any buttons.
Explanation? I have no idea!
Problem 3:
After closing the pano the memory it used isn't released.
Looking at the Forum history this is a well known problem, but the cure was supposed to be to remove the skin, and I did remove the skin!
vr.cleanup();
removeChild(loader);
vr.pano = null;
loader.unloadAndStop();
Seem to work, but my traces tell me this:
loader.content = null
vr.pano = null
vr = [object PanoPlayer]
loader = [object Loader]
And memory is NOT released!
These are serious obstacles for using (a series of) Pano2VR panoramas inside bigger Flash applications, and it would be VERY nice if they could be removed!
Cheers!
Erik
Here's a link:
http://tinyurl.com/Direct-to-FullscreenPano
As such it is no problem to make this happen with a small Flash application as a helper, but like always there's some snakes in the grass.
Problem 1:
Letting that helper open a pano 'the normal way' takes forever, the (default) progress indicator in the skin seems to never end counting, and sometimes the pano doesn't load completely at all.
In short: this method of loading panos is to be avoided like the plague!
However, if I suppress visibility of the loading Pano and let my own progress bar in the helper do the counting, that very same pano loads like lightning!
Explanation? I have no idea!
Problem 2:
Pano2VR skin elements have a strange (= bad) effect on processor load.
A pano with one or two buttons doing absolutely nothing generates significant CPU usage, whereas the CPU shows no activity with a version of the same pano without any buttons.
Explanation? I have no idea!
Problem 3:
After closing the pano the memory it used isn't released.
Looking at the Forum history this is a well known problem, but the cure was supposed to be to remove the skin, and I did remove the skin!
vr.cleanup();
removeChild(loader);
vr.pano = null;
loader.unloadAndStop();
Seem to work, but my traces tell me this:
loader.content = null
vr.pano = null
vr = [object PanoPlayer]
loader = [object Loader]
And memory is NOT released!
These are serious obstacles for using (a series of) Pano2VR panoramas inside bigger Flash applications, and it would be VERY nice if they could be removed!
Cheers!
Erik