Hello Tllewell,
All of the input functions of the Lua IO library appear to be broken. io.read() (in any mode), io.lines(); nothing works. I even tried io.popen, which I am not sure even works on Windows. Major parts of the systems I've built over the last two years are broken and most of my trade management does not work.
Why in the world would you break parts of the way the language works? It's not the core language, but people sort of expect the standard libraries to work.
We try to provide maximum compatibility with standard Lua libraries, but sometimes we need to change standard functions. For example, we had to make our own implementation of io functions to support Indicore packages (indicators can read files directly from packages) and secure user data (starting from the next TS version, users will be able to restrict access of indicators to the file system). Unfortunately, the current implementation has errors that have not been detected in time. In fact, even in the current production TS version you can work with files via io functions, but you need to use non-standard read modes.
In attachment you will find an indicator that displays currently supported modes. This indicator was tested on a production version of the Trading Station.
I should have said something, but at the time I became more concerned over the way getSyncHistory had been broken than the way the IO library had been broken.
Could you explain what exactly the problem is with getSyncHistory?
Our test and PIVOT indicators that use this function work fine.
Unfortunately, despite our thorough testing, sometimes we miss errors.
We usually pre-release TS DEV versions with new functionalities so that developers of indicators and strategies could check them for compatibility with new versions and we could fix bugs before releasing to production.
We would be very grateful for any feedback on using Dev versions and for messages about any bugs you see. They help us improve qualityof our product and reduce the number of possible problems.