Go to Multicharts. Don't look back
Unacceptable TradeStation Bugs ???
- Thread starter NoVoodooHere
- Start date
Adapative or otherwise variable lengths can be implemented within what otherwise is a series function ...via knowning what you're doing. This problem is not unique to TS. It's unique to series functions. If Multi-Charts includes series functions then MC suffers from the same limitations.
Most programmers will tell u it's impossible but that's because they're stuck, unable to think for themselves, at least in this area. But the solution is simple.
Most programmers will tell u it's impossible but that's because they're stuck, unable to think for themselves, at least in this area. But the solution is simple.
TradeStation has gotten better, much better. TradeStation did fix the order of precedence for mathematical operators, probably long before I became a client. TradeStation has greatly improved their EasyLanguage since 2000i.
However, EasyLanguage still has some problems such as not being able to place variables in "series" functions such as RSI, XAverage, etc... If you place variable "RSI_length" in RSI(Close, RSI_length) and then try to use that in RadarScreen, you will get the same result beginning from the first RSI_length assignment no matter what you change RSI_length to. TradeStation should have fixed this long ago but I guess they never did. I'm not sure why. However, this has not impeded my ability to use EasyLanguage. It's more of an annoyance than anything else. Using an Input instead of a Variable is a workaround. This variable problem does not affect standard EasyLanguage functions such as RateOfChange, only series functions.
My TradeStation 9.1u29 install is 4 years old and another small bug has cropped up which I must work around. Speaking of, TS 9.5 u14 is still in BETA.
Another problem I have with TradeStation is you must build everything from the ground up. You must write everything with EasyLanguage from scratch. Otherwise, you must pay for indicators which can get expensive. Unless you are an expert EasyLanguage coder, this can become very time consuming and difficult. Even the simplest tasks can take forever. So instead of making money, TradeStation users must tinker with EasyLanguage. I am not an expert EasyLanguage coder.
A positive update from my previous post: I did learn how to use the basics of TradeStation Objects. I now know what the different TradeStation Objects are and what they do. Eventually, I will learn how to code fluently in EasyLanguage, even in Objects. However, this will probably take far longer than I want. In the meantime, I will be forced to use online charting tools such as Stockcharts.com in addition to TradeStation.
Write a series function that stores the results of all the lengths u could ever possibly need, where every series function call is replaced with inline code. If currerntbar changes the length from the previous bar then the series function accesses the most recent stored value for the new length rather than the stored value for the old length.
If u don't want to store all that data, a separate solution would be to loop thru the necessary history to prime the inlined version of code that replaced the series function calls...but only when the length changes. If the length remained the same on some bars then it wouldn't have to loop thru all that history (on those bars). IMO that's a lesser hack but ymmv.
If u don't want to store all that data, a separate solution would be to loop thru the necessary history to prime the inlined version of code that replaced the series function calls...but only when the length changes. If the length remained the same on some bars then it wouldn't have to loop thru all that history (on those bars). IMO that's a lesser hack but ymmv.
Last edited:
Do you think you could give us an RSI example, for those of us who are not expert EL programmers?
I already gave u 2 solutions. I'm not going to write it for u but I guarantee both solutions work. And u can't buy my time, for any price.