Closed ComBatVision closed 5 years ago
Could you also look at my comments at https://github.com/missioncommand/mil-sym-js/issues/33 The issue was not solved.
Try this and let me know. There was a java call that didn't get changed. And I updated the references as you said in issue #33 sm-bc.zip
I can test only on monday. Left my notebook in office.
пт, 15 бер. 2019, 21:10 користувач Michael Spinelli < notifications@github.com> пише:
Try this and let me know. There was a java call that didn't get changed. And I updated the references as you said in issue #33 https://github.com/missioncommand/mil-sym-js/issues/33 sm-bc.zip https://github.com/missioncommand/mil-sym-js/files/2972551/sm-bc.zip
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/missioncommand/mil-sym-js/issues/34#issuecomment-473408881, or mute the thread https://github.com/notifications/unsubscribe-auth/AL6KihKGdCDAA_1Khra2quxAS0F0wxvPks5vW_A0gaJpZM4b2tdF .
No more "TypeError: java.io is undefined", but GeoPixelConversion3D from issue #33 is still in the same state and I do not see any changes related to this in the last commit 3902e9ec6ea3bbaa408cfa40aefc522b483c13c1.
The issue #34 can be closed. Lets continue discussion in #33.
Sorry, missed GeoPixelConversion3D in the commit somehow.
We'll carry on in issue #33
When some erorr occurs inside mil-sym-js, than browser shows hundreds of following errors in log. It looks like some part of code migrated from JAVA to JS tries to create error log file using java.io.* classes.
It is not a critical error, but could you cleanup this case to be able to see real error in mil-sym-js. Because now real error is one of 100 this log errors.