[x3d-public] Errors in serialized X3D Python (my collection)

[Brutzman, Donald (Don) (CIV)]

Thanks for activity John.  We have a big research event going on this week at NPS that is preventing my from keeping pace - will catch up when possible.

It is OK to keep the .future.py files active, the build scripts for X3D Examples Archives are tuned to the filenames.  Since they showed differences, recommend the checked-in version continue with both conversions since that aids in debugging.


On 4/9/2019 8:43 PM, John Carlson wrote:
> There were some errors on collision objects using setProxy when they shouldn’t be.
> 
> These are caused because proxy is after children in mapToMethod.js.
> 
> We can override in mapToMethod2.js  I think.
> 
> I did that.
> 
> I have stopped running *.future.py files in pyjnius/build.xml  To add back, remove future.py line.
> 
> Fixed MFBool arrays, checking now.
> 
> John
> 


all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman