<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>No, it’s not okay to keep *.future.py files unless we are willing to make the changes to X3DJSAIL/PyJNIus/Python/Java to make them work (fix some examples to make them work, like abox.future.py). They are not working on my system (no output)!</p><p class=MsoNormal>But I can’t tell, because of a smokescreen that someone created in my python serializers to generate identical filenames!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Do I need to go through svn logs?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Perhaps I should send you some python files that don’t work? Would that be better?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dang, missed my coffee today. Maybe later.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:brutzman@nps.edu">Brutzman, Donald (Don) (CIV)</a><br><b>Sent: </b>Tuesday, April 9, 2019 11:20 PM<br><b>To: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: Errors in serialized X3D Python (my collection)</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 4/9/2019 8:43 PM, John Carlson wrote:</p><p class=MsoNormal>> There were some errors on collision objects using setProxy when they shouldn’t be.</p><p class=MsoNormal>> </p><p class=MsoNormal>> These are caused because proxy is after children in mapToMethod.js.</p><p class=MsoNormal>> </p><p class=MsoNormal>> We can override in mapToMethod2.js I think.</p><p class=MsoNormal>> </p><p class=MsoNormal>> I did that.</p><p class=MsoNormal>> </p><p class=MsoNormal>> I have stopped running *.future.py files in pyjnius/build.xml To add back, remove future.py line.</p><p class=MsoNormal>> </p><p class=MsoNormal>> Fixed MFBool arrays, checking now.</p><p class=MsoNormal>> </p><p class=MsoNormal>> John</p><p class=MsoNormal>> </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>all the best, Don</p><p class=MsoNormal>-- </p><p class=MsoNormal>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu</p><p class=MsoNormal>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</p><p class=MsoNormal>X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>