Posts made by fxDreema

The yellow line is always there, it's just hidden from red and green lines

Buffer 0 always returns price levels, nothing interesting there. But you can try "Indicator appear" or "Indicator disappear" on the other two buffers.

Well, when it does not happen to me I have no idea what it can be I did that and the file is updating right when I start the program. But I have very few test projects over there, so what could be wrong. Try to delete the other file - list.ini. Or try with no projects.

You can try "Indicator appear" or "Indicator is visible", if these does not work, then then it is something more specific.

What is the value of buffer 0 when the color is not yellow, and what is the value when it is yellow? You know that everything is comparing values, as all the buffers always gives you numeric values.

This one? http://prntscr.com/55adfk

Wow, it's not good when things goes in that direction, to use too many blocks, which are otherwise the same. It will probably work, but it does not look very good. But maybe I just have to make a single block to do all this stuff

And again. Please, when you want to show something, just make brand new temporary project clear from weird stuff. I do this for many people, it's not that hard. I always use the same project name ".fxDreema", so it is alway there in the folders. Like this one that I just created to demonstrate that the trade is closed on 10 pips profit: https://fxdreema.com/shared/EA6fwpDVb

It is 511 in the project, not 510.

The profit of a single trade can be get. To compare that to the sum of other two is a little bit more complex, as some variable should be used to collect that profit.

From what is it now, It must close some trades anyway.

But mine changes And I don't remember doing modifications that can make this to fail What if all the installation is in nother folder?

Martingale is inside "Buy now" and "Sell now" blocks and there are few parameters to control it. If needed, these parameters can also be controlled via variables

Normally in "Condition", indicator values from the current candle (Candle ID = 0) are used, which means that you can detect crossover in the middle of the candle. At that very moment the crossover will be true and visible. Then, after that candle is closed, nothing will look the same as few moments before. Sometimes crossover happen and then the price goes back and at the end of the candle it looks that there was no crossing at all. Just look at the indicator while it's working - all the indicator points are staying still, but the very newest one is moving on every tick, up-down, up-down.

I think I will forbid using blue and pink blocks in the same group of blocks in future.

This is the regular single-block trailing stop: https://fxdreema.com/demo/mt4-trailing-stop
This is basically the same, but using multiple (pink) blocks: https://fxdreema.com/demo/mt4-loop-trailing-stop

There is no reason to put "Trailing stop (each trade)" inside the loop created by "For each Trade". "Trailing stop (each trade)" has it's own loop inside! More than that - this block is designed to work most of the time, if not all the not. It's not to be hidden behind some "once per trade".

There is a pink block called "modify stops".

Follow the logic in the loop. "For each trade" loads each trade one after another, in your case - on each tick. What's next - "once per trade/order" - this block remembers ticket numbers, it passes 1 time for each trade. It will pass the very first time that it sees your trade, can you expect that it will pass again when the trade has some profit or loss... basically when some time passed? Not at all. What if you put that block after "pips away"?

I think I know what you want to do, it's something that I still don't have in a single block. But with multiple pink blocks is possible. Something like this: https://fxdreema.com/shared/BxqrMwCVb It's not very elegant, but it should do the trick. The only problem is that "once per trade/order" has temporary memory and if the EA is restarted, that memory is lost.

Use Candle ID = 2 or more, I does not work with 0

Classic
https://fxdreema.com/demo/mt4-wrong-closing-rule
https://fxdreema.com/demo/mt4-events
https://fxdreema.com/examples

Blocks like "No trade is running" accept single value

It's now working using the native WebRequest() function. Make sure that the url looks like this "http://..."

Don't believe this importer very much Sometimes it reads everything correctly, but sometimes it fails. Here is more about this topic: https://fxdreema.com/documentation/proj ... indicators

What do you want to control? There is a parameter "Group #" that is a form of magic number, this is the way to have groups of trades within the same EA. The default value is empty (0), but you can set it to 1, 2, 3... something numeric.

This will not work, the chance is to put 5 trades in a row

So you want to get the equity when a new day comes. Then I will suggest "Once a day" -> Get that equity in a variable + calculations if needed
Then, at a separate group of blocks you can compare that value with...

1. In Condition (Account -> Equity) you can get the current global equity, the one you can see in MetaTrader
2. With block "Check current unrealized profit" you can get the profit from a group of running trades. This is not the global profit, because you can have other trades outside this EA.
3. Something else, like the total profit from all trades closed today + the currently running ones. Well, this will require some more blocks

Well, this block is normally for small delays, I never tested it for long times to be honest. What it does is to pause the EA to the point where it is right now, and then continue from that point. In theory, it will work, so you can test it.

The alternative is, (again, in theory) but there is no special block for this, is to work with the time in some variables. If the variable is set to the time that is older than the current -> continue, otherwise don't do anything below. And set this variable to some time in the future where you want to set that delay. Eventually, the current time will reach that "future" time and the delay will expire. Then you can do that again.

Now that I'm explaining this, I think there are some blocks for that For example "Once per minutes" or some other "Once...". But before using one of these, read it's description. Even I forget how they are working sometimes