Hi Regina,
the dr3d:scene scene is - as in the model - the binding element between
3D content and 2D objects. It has two objectives:
- be a 2D element which defines where the 3D content is to be rendered
to, it's z-sorting and other 2D attributes, hence the 2D stuff like
svg:width and svg:height, these should be the 2d attributes of the 3D
scene in it's role as 2D object
- be the root of a 3D scene, with a hierarchy of 3D objects, lights and
camera definitions which will all be rendered to a 2D 'bitmap' content
(except the 3D shadow, that is another beast and creates 2D shadow
'behind' the rendered 3D bitmap, but as vector data)
The camera for an inner 3D scene is ignored (only the outmost one makes
sense). I would guess there was no easy way to make an extra-definitopn
for a 2nd 3D scene which allows both. Toe other sense of inner 3D
scenes is a simple group object mechanism (extensively used in 3D charts).
HTH!
On 21.10.2013 09:44, Regina Henschel wrote:
Hi all,
The element dr3d:scene has the attributes svg:width and svg:height in
the ODF specification. What do they mean?
When I set a special width in AOO, I can see, that the picture of the
3D-scene is stretched to the given width. That is the same behavior in
AOO as with width on an OLE object.
But following the spec a dr3d:scene can have other dr3d:scene elements
as child elements and I have no idea, what makes sense then.
Similar problem is with the attributes, which describe the camera.
What is the sense of an own camera for an inner 3D-scene?
Kind regards
Regina
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
