Apparently, the key and keyValue are not maintained in output X3D encodings, using this:
CoordinateInterpolator24 = x3d.CoordinateInterpolator()
CoordinateInterpolator24.DEF = "ci"
CoordinateInterpolator24.key = [0,0.5,1]
CoordinateInterpolator24.keyValue = [(-23.495, 90.55, -8.13),(-28.825, 91.31, 0),(9.77497, 126.11, 0[snip]
Scene9.children.append(CoordinateInterpolator24)
I guess I'll have to revisit my Python Serializer.
Hmm!
Diff:
This also fails:
$ grep Interpolator flipp.py|cut -c1-100
ScalarInterpolator23 = x3d.ScalarInterpolator(key=[], keyValue=[])
ScalarInterpolator23.DEF = "si"
ScalarInterpolator23.key = [0,0.5,1]
ScalarInterpolator23.keyValue = [0,1,0]
Scene9.children.append(ScalarInterpolator23)
CoordinateInterpolator24 = x3d.CoordinateInterpolator(key=[], keyValue=[])
CoordinateInterpolator24.DEF = "ci"
CoordinateInterpolator24.key = [0,0.5,1]
CoordinateInterpolator24.keyValue = [(-23.495, 90.55, -8.13),(-28.825, 91.31, 0),(9.77497, 126.11, 0[snip]
Scene9.children.append(CoordinateInterpolator24)
I don't get it. Clueless at this point.
I've been looking at x3d.py. Nothing pops out.
Here's a fairly short program that shows the issue. Feel free to truncate the keyValue a bit.
For example, interp2.py, attached, works.
It's got something to do with the DEF. When I take out the DEF from the Interpolators, I do get key and keyValue.
Hmm
Last edit: John W Carlson 2026-02-08
This seems like a half decent solution.
There is not a problem with x3d.py
Here are two examples showing Python programming with CoordinateInterpolator and CoordinateInterpolator2D
and, in general,
Last edit: Don Brutzman 2026-02-08
Yes, I was able to verify that the X3dToPython.xslt version worked. I will
work towards putting DEF/USE as a constructor parameter. This seems to fix
the problem in one case.
John
On Sun, Feb 8, 2026 at 11:30 AM Don Brutzman brutzman@users.sourceforge.net
wrote:
Related
Tickets:
#91