79 |
- Should the child vobscene define the number of coordsys |
- Should the child vobscene define the number of coordsys |
80 |
in the beginning to replace with coordsys from the parent? |
in the beginning to replace with coordsys from the parent? |
81 |
|
|
82 |
|
- What about coordinate system 0? Should it be special in the child |
83 |
|
and always correspond to cs 0 of the parent (i.e. unit transformation)? |
84 |
|
This is made problematic by the twim roles of coordinate system 0: |
85 |
|
on the one hand, it's the "root" coordinate system, |
86 |
|
on the other hand, it's the "no transofrmation" coordinate system. |
87 |
|
|
88 |
|
RESOLVED: It should be special. However, we should start a new |
89 |
|
convention: coordinate system **1** is the "root" coordinate system, |
90 |
|
and **0** remains the "identity" coordinate system. |
91 |
|
|
92 |
|
|
93 |
- How do we get the coordinate systems into the child vobscene? |
- How do we get the coordinate systems into the child vobscene? |
94 |
|
|
95 |
- Matching? |
- Matching? |