So take this example, where 'pf' is a rectangle that exists in the plugin since the beginning (added in flash;the origin in the center) and 're' is instantiated in actionscript. 'tf' is a textfield:
Code
// The data to display on the plugin
re = new RectangularMovieClip();
// Scale plugin based on stage and dimensions of the data
pf.height = stage.stageHeight * 0.9;
pf.width = re.width * pf.height / re.height;
// Scale data to be slightly smaller than the plugin base
re.width = pf.width * 0.95;
re.height = pf.height * 0.95;
// Center the data in the plugin
re.x = re.width / -2.0;
re.y = re.height / -2.0;
// Textfield to show if the data has the correct dimensions
tf.text = re.width + " x " + re.height;
tf.x = 0; tf.y = 0;
// Add the data and textfield to the plugin to be rendered
pf.addChild(tf);
pf.addChild(evt.target.content);
Alles anzeigen
What happens is that the plugin base (pf) appears over the panorama with exactly the CORRECT dimensions and position. However, BOTH the textfield (tf) AND the rectangle (re) show up *HUGE*! But I really mean, HUGE, like, over 400% as big as they should be.
And the funny thing is, according to the CONTENTS of the textfield tf, the rectangle re's dimensions are correct!
What's going on here? Does krpano do anything funny to the plugins' children that I'm not aware of?