Posts made by fxDreema

Yeah... after I'm creating some problems I must take care of them

__Yepp. You must consider each customer with his needs and wishes. I don't know how it would be better to realize SRSLs...[/quote:1prbv5dn]
What means "SRSL"? I know that S&R means Support and Resistance, and SL is Stop Loss, but I've never seen SRSL before

Ok, this is ready to test. I added a new option in "Options -> Current project options", you will see it. At first test it worked to me, but I used backtester because markets are not working at the moment. The time used for calculations is the local time, but in backtest it is the candle's time (aka server time). So you can try with 3600 seconds (1 hour) for example and see how many candles are skipped. Better try it first with a simple project, not the one you have now.

Now "Current project options" is a total mess, so I must take care of this as well

The idea is actually good, it makes virtual stops even more functional. I can add it to the project options. Well, when I think more about it, someone in the future may ask me why it exista as a global project setting instead of being in each block like independent option... so yes, maybe there are weird ideas sometimes.

You must be serious

Sorry that I'm not fast. I am doing many things, and also before I create some new feature I like to think of it for a while. All this is because of the eventual problems that can appear... which unfortunately still appear more frequently than I want

These days (and weeks) I am more focused to do some optimizations, recode and touch the details. I think I skipped help materials and examples for too long, so I must do some updates there. Also, I plan to move the website on a different server soon, if everything is ok.

So now indicators data cannot be shared to the project. Bugs are always running after me
Nevermind. Now you use "Shrink" blocks that are created to shrink SL/TP with some pips, and the input value here should be like this: 5, 10, 15, 20. Optionally it can be in what I call "digits" format like this: 0.0005, 0.0010, 0.0015, 0.0020. But not in price level format like 1.2837. There is no reason to shrink SL with 1.3265 pips, for example.

I found a little problem in the last build. The problem is that the project is not listed, but this can be repaired by removing this file -> Data->Username->experts->list.ini. I also reuploaded it, so you can clear this file, then download the last fxDreema again to not have this problem again. And of course, sorry for that

I'm testing here virtual stops, it looks fine. Now I don't know why your stop is not triggered. So, there are no errors, nothing?

What is the normal timeout in your opinion to wait before triggering stops - Seconds, milliseconds? And where it should comes from - server time or local time.

It checks if the trade is beyoud SL or TP line, and if it is - it should close it. This situation happens on every tick. At least on backtest it works. Now I'm trying it on demo...

Do you have some error messages? Is the line name like this "#ticketnumber sl"?

About the spikes question - this can be done for the hidden stops only, I think.

This is well known situation with Moving Average. This indicator does not guarantee profits, it just calculates something and draws a line.

To know if MA is rising or falling, you must compare two values from it. Oldest value below the newest => rising. Otherwise => falling. You can also check "Indicators" category.

Blocks 6 and 13. Let's say that there is an option inside called "Filter by type"

Your "No position is running" is working for both, buys and sells. If there is a single trade, no matter what type, it will not pass.
If you connect 3 blocks one after another, this is natural AND and you don't need AND blocks.

Very stupid mistake from me, but everything is fine. I even found some libraries that must be deleted, but for some reason they are still there. I'm not sure about that, but you can check them - both on the top.

This problem also means that I must do another local build. If there is someone else that is using Library Studio and has the same problem - contact me.

Hm. It looks to be database reading problem. I edited some things and maybe I missed something. Your libraries are ok and blocks are actually working, don't remove them. I will check what is the problem and you will see them all again. Thanks for the report by the way.

At first I think it's not so good idea to mix trailing stop, break even and custom stops manipulation - all at once
Trailing stop and break even blocks works on it's own, they can manipulate many trades and they does not keep records of which of them are modified. But if you construct everything with pink blocks, you can keep some records with custom variables, "(in loop) Once per trade" or "(in loop) Modified status"

Haha. Remove about 100-150 because in phpBB first 50+ users are reserved for bots, and there were spammers in the beginning when before I added the antispam question to register

This is real situation from this morning. It happened to a friend of mine with AVA broker. I changed the name of the EA in the log:

08:13:17 EANAME EURUSD,M30: Error occured. Error code 129
08:13:19 EANAME EURUSD,M30: Error occured. Error code 129
08:13:21 EANAME EURUSD,M30: invalid slippage for OrderSend function
08:13:21 EANAME EURUSD,M30: invalid slippage for OrderSend function
08:13:21 EANAME EURUSD,M30: Error occured. Error code 4051
08:13:23 EANAME EURUSD,M30: invalid slippage for OrderSend function
08:13:23 EANAME EURUSD,M30: invalid slippage for OrderSend function
08:13:23 EANAME EURUSD,M30: Error occured. Error code 4051
08:13:27 EANAME EURUSD,M30: open #10365265 sell 0.30 EURUSD at 1.30140 ok
08:13:29 EANAME EURUSD,M30: Error occured. Error code 136

Weird errors. This is ECN broker, so first the trade must be sent, and then stops to be modified. Everything happens in 2 steps - OrderSend() and then OrderModify(). The actual problem here is not that the trade has troubles to be opened, but after that - when stops must be placed. You can see that error 136, which means... "Off quotes".

Leaving a trade without stops can be very dangerous sometimes, even if the EA itself is not scalping. For this EA - missing stops caused more trades to be opened because of wrong part in the code.

For example, in non-ECN brokers there are 2 outcomes - to create a trade with stops or to not create a trade at all. With ECN broker you can be easily found in a situation with a trade with missing stops.

So, be careful with ECN brokers. I know that everyone say that ECN is better, but obviously this is not exactly like that. It looks that every ECN broker has at least one more chance to fail - in OrderModify().

"Start trades loop" or "Start pending orders loop" is missing. (in loop) blocks **needs **"Start trades loop", otherwise we don't know with what trade or order are they working with.
Most of the (in loop) blocks are designed to be able to work in with trades, orders, buys, sells... all of the variety. You have pending orders blocks in this project. So can you guess, block 9 serves what - buy trade, buy order, sell trade or sell order? If you ask me - I don't know.
Put some "Start pending orders loop" somewhere.

Also, I don't think you need 10, 15, 16, 21 to slide up and down to the same place the just-created pending orders, or I don't understand why is that...

Done, also for vertical lines and rectangles. But on MT5 for some reason there is no effect

I don't understand fundamentals very well, but I know this indicator http://www.best-metatrader-indicators.c ... indicator/
Well, I tried it once to see how it works, but not in EA, so I don't know how it can be used in EA (if it can). Also I know that there are other programs and you can search in forexfactory.com.

Let's say that most of the time I'm programming php, javascript, looking for bugs and new features, explaining things to people, browsing MQL functions, dealing with the server, doing the local version. After all of that I am not so focused on the people's strategies, especially when they come to me with parameters with checked inputs and with mixed rules like Ryan Jones MM + Trailing Stop + Break Even + Loop.

When there is a problem with some block, what do I do? I isolate it, better on a different temporary project. I connect 2-3 blocks if needed, but the idea is that there must be nothing to interfere with the one I am checking.