But it seems wrong way! Why do View3D should detect size changes by itself? Application or some UI component should monitor changes in its (or stage) size and apply properties of View3D.
Before (in 2.0.0 release) I was able to do anything to View3D, setting its x, y and clip properties, depending on my needs. Now View3D desides for me when to be resized or not. Am I totaly wrong or Away3D should be flexible as it used to be before? On 25 фев, 18:23, Peter Kapelyan <[email protected]> wrote: > I think this was done so that the clipping can detect resizing the SWF, I > don't think it was working right before. > > Thanks for adding it to the issues. > > -Pete > > > > > > On Wed, Feb 25, 2009 at 5:08 AM, Diomas <[email protected]> wrote: > > > Hello, > > If I try to render View3D that is not included in display list, I get > > this error: > > > TypeError: Error #1009: Cannot access a property or method of a null > > object reference. > > at > > away3d.containers::View3D/updateScreenClipping()[I:\dev\lib\Away3D > > \src\away3d\containers\View3D.as:801] > > > Same issue with View3D in flash10 branch (on 811th line). > > > The problem is View3D tries to use his stage property which is null. > > > Why do View3D need any links to stage at all? Why not to use its own > > x, y properties for clipping? > > > Its a problem, because now if i want to get, for example, few > > snapshots of some scene and hold it in memory or draw it into some > > BitmapData, I have to put View3D somewhere in display list even if I > > don't need it actually. > > > Added to issues. > > -- > ___________________ > > Actionscript 3.0 Flash 3D Graphics Engine > > HTTP://AWAY3D.COM
