search

PiRSquared17 / alembic

Automatically exported from code.google.com/p/alembic
Other
0 stars 0 forks source link

Need Vector4 and Point4 Typed Properties? #125

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently Alembic doesn't support Typed Properties of Vector4 or Point4.

Since Imath doesn't have a Vec4 it isn't obvious to me what type we use to 
encapsulate one of these.  (Quat and Color4 while the right size, doesn't make 
much sense)

Original issue reported on code.google.com by miller.lucas on 17 Dec 2010 at 6:59

GoogleCodeExporter commented 9 years ago

Original comment by miller.lucas on 18 Jan 2011 at 9:48

GoogleCodeExporter commented 9 years ago 
Note, check with Joe because he started a thread with RnD about next 
OpenEXr/ILMBase release. How important is this, or rather how hard should we 
push on this?

Original comment by ble...@gmail.com on 8 Jul 2011 at 1:35

GoogleCodeExporter commented 9 years ago 
This isn't important enough to push on.  Many facilities would be reluctant to 
support a new version of OpenExr/ILMBase in the short to midterm.

Original comment by miller.lucas on 8 Jul 2011 at 2:21

GoogleCodeExporter commented 9 years ago

Original comment by ble...@gmail.com on 8 Jul 2011 at 2:24

GoogleCodeExporter commented 9 years ago 
The Point4 case was primarily for handling nurbs weights. Since we opted to 
make that an optional float array property, there isn't an immediate need for 
this to map to any native client type.

The equivalent data footprint can be achieved by using "array extent" feature 
of GeomParam.

Original comment by steve.lavietes@gmail.com on 26 Aug 2011 at 12:25