Hi, I use this code to send a limit order (for some unknown reason I have to use a stop order to get it to work as I expected a limit order would do, dunno why....). But the problem is that even though I've hardwired Type=4 it sends one stop order
I could figure this out on my own but it would take weeks or months of forward testing, so I'd just like to hear what your experience is with this. Some indicator driven EAs can work quite well, but its well known that these need frequent optimizing
Hi, This is a MA indicator that is reading MA off a higher TF and used in a lower TF... In its current state the line appears as a staircase, drop it on a 15M TF and you'll see. I want it smoothed so that there is a distinct change for every low TF
Hi, Some EAs perform spectacularly well when backtested using controlpoints mode, but quickly empty the account when tested in every tick mode. I read the help file about the modes but didn't get any smarter... Would it be possible to apply some sort
Hi, anyone wanna modify this function a little ? Its a very useful tool for testing / debugging / visualizing stuff. Problem is that it places multiple Vlines at the same bar (typically on for each tick) and even a short testrun can result in
Just FYI I have never used Vista, and never will. But I have a fellow trader in another city with Vista (Home Premium) on his PC, and he could not get my EAs to work. All sorts of errors appeared in the Journal, so I went in via RDP(or similar) and
Topic basically says it all. I have a pal in another city and he is trading manually and getting very good results. I doubt he has much of a trading plan, non the less he is almost doubling his account every week. If I could take his history and show
It seems to work ok on test, not getting any errors. But still not 100% sure its ok. Can you check it over ? //---------- Trailing Stop --------------------------- void TrailingStop ( double TrailingStop , double TrailingStart , int TrailInterval )
Hi, here is a test EA for checking my (soon to be) drop-in TrailingStop routine. The TS seems to work but I get flooded with " OrderModify error 4051" and "invalid ticket for OrderModify function" errors. Just run the EA on 1M
Can anyone see whats wrong here? It calculates true risk, that is $ loss if all open trades goes to StopLoss, and displays that in an info board in the UL corner. But it shows too low values, at least some 500% too low. Seems to vary from one symbol
I'm calling this function from the EA's deInit, But none of the objects are deleted... Any idea why ? //---------------- DeleteInfoBackground ------------------------- void DeleteInfoBackground ( ) { //Objects created has names like: RecW11, RecW12
I want my EA to work seamlessly with 4-digit brokers and 5-digit brokers AND 4-digit and 2-digit symbols (E.g EURUSD and USDJPY ) with 4-digit brokers AND 5-digit and 3-digit symbols (E.g EURUSD and USDJPY) with 5-digit brokers AND have external
Hi, I recently had a bad experience with unadequate MM... Now I'm going to do it RIGHT. Goal: Find lot size for a given true risk ( in $ or % of Balance) so I know beforehand how many dollars (or %) will be lost if the worst happends Given: -Balance
I am NOT accusing MetaQuotes for for anything here, I'm only speaking up on some concerns that I have. I would like MetaQuotes to submit their sourcecode for scrutiny by independent western security firms, and have the code ( including updates)
As a safetymeasure I call this early in the Start function: //---------------- SaveAccount ------------------------ bool SaveAccount ( ) { if ( AccountBalance ( ) < BalanceCutOff ) { Alert ( "In order to protect the account "
Well... after about 9 months of intensive programming it finally looks like I've succeeded with a signalling system that really works. This "unreal" graph is a backtest result. But after two weeks of forward testing on demo the preliminary
Set out to make a super simple indicator, shouldn't take more than 15 mins I thought...Not this time! Indicator: show spread history (as data comes in) as bars in a separate window. Problem: all indicator bars are cleared then changing TF. Looks like