0 Members and 3 Guests are viewing this topic.
Adriweb and jimbauwens definitely talked to TI about the problem... to no avail, at the time of this writing.
also you might convince TI to put print() back if you tell them about the educational purposes it could have (robotics and so)
...We redirected the output of the print command to the console log of the integrated script editor. In retrospect, we should have maintained the print connection to stdout until the script editor console was fully implemented. Do you see value in continuing to send print output to stdout in addition to the script editor console?
I submitted a change request to reinstate output to stdout. I cannot guarantee the change control board will approve the change in time for the next software release. I quoted large parts of your email in the request.
Jim,The change control board rejected the request. It comes too close to the end of the current development cycle. I'll add the change to the requirements for the next development cycle.
I forwarded the request to turn print() back on in Lua to the product definition manager who defines requirements for Lua scripting. The feature should be a requirement for the next release. I'll check with him on the status of feature.
There have been so many things that we wished, but they did not grant (and sometimes, had to grant ourselves), that we should not get ourselves excited until it's done
@Jim Bawens and what if TI included also a "listen()" to receive data from the RX serial?EDIT: by data I mean text, of course... even char by char would be awesome...