Posts made by fxDreema

It's probably the setting that you don't understand. By "Opposite stop" I mean TP if you are moving SL or SL if you are moving TP. After all, Trailing Stop can actually be used as Trailing TP

Here is some idea: https://fxdreema.com/shared/HBgwoQHnc

This is I think exactly what you want, but I'm pretty sure you will not understand what is going on here: https://fxdreema.com/shared/NNuCCXO9d
I use one extra Variable to change the amount of pips that must be traveled, only because I can't find how to get the OpenPrice of the latest child-trade. And by "child-trade" I mean... you will see how you start with one trade and how each following trade is visually connected to the initial one. This is done by MetaTrader itself

I was also thinking about this, but something doesn't work with lot sizes: https://fxdreema.com/shared/dCa88msrb
90% of the first lot size is 0.9 if the lot size is 1. But the next order calculates 90% of 0.9, which is 0.81 (not 0.8). And when you reach lower levels the numbers deviate more and more. This is because each following lot size is % of the previous one, not of the first one

Trailing stop is a process of continuously monitoring the distance between the current price and the SL level. If that distance becomes too big, then SL is moved. But it's important to put SL at appropriate place.

For a Buy trade, this is the process:

if ASK > SL + STOP + STEP then move SL to ASK - STOP

... where ASK and SL are price levels and STOP and STEP are values like 0.0010 added to those price levels

Something is probably wrong with the STEP value. What is it?

Yes, this is very ugly. I can feel the problem, because I also have it when I'm programming something. I have seen such pictures many times before and for sure I need to do something about it, but you can also follow some good programming practices.

• It's important to separate things. I can see you have some groups of blocks separated from other groups and that's fine until you make connections between them. And obviously, when there are too many connections you can't even see what is connected to what anymore. So try to isolate each group of blocks and don't connect one group with another... at least not with so many lines. There is also a block "Run blocks". Also, note that blocks numbers can be also words and if you use "Run blocks" I will suggest to work with blocks who have words instead of numbers.

• It's important to also combine things. If you have 2 or more groups of blocks that contain the same blocks, try to combine them. The idea is to have only one group of blocks, but to run it multiple times. Something like functions in programming. Well, functions have input arguments, while blocks don't. But Variables can be used in blocks, which is something similar to the arguments.

• Don't put everything in the visible area. By the way, you can also put some Areas here and there and separate groups of blocks that way.

Interesting question. I was trying to make something, but if I start with a trade and then that trade is partially closed multiple times, the problem is that each following child-trade has different ticket number, but it's OrderOpenPrice() stays the same as the one from the original mother-trade. So now I'm not sure how to get the latest... let's call it Open Price of the Child.

I was also thinking for something with pending orders in gridusing Grada, but the problem that I found is that when I want to open each one with different lot size (using Gradation settings), at some level calculations are going wrong because of the lot step. Which is something that I'm gonna try to fix.

Those purple blocks are to be used only under "on Trade". Blocks like "Bull candle" are to be used under "on Tick". And I'm not sure about these "Close..." blocks...

I think you need to look at some examples - https://fxdreema.com/examples/

But do you use that plugin or it's naked?

Now working?

In Condition there are Adjust fields and there you can write something like +0.0005 or even +5pips. And yes, candles are made by Bid prices only. Buy trades are opened at Ask, so for them there is always some offset from the candles. If you care about that.

What "looking back" means to you? This is to walk in each candle one after another and look at the value of the indicator for each candle. But if the value is like this, what can you expect

Maybe something with Safari. If you have Chrome, try with it. And for Chrome there is an extra plugin that can be installed to dowload files directly

If know what I am touching in the day. I don't post most of the fixes I do, but I know that if today I am doing something specific, I can expect in the end of the day to have reports for problems about this thing. But when someone reports about something else and it doesn't sound familiar to me, then it's something that was there for long time and I didn't noticed it. Or something very specific is wrong on it's side. But anyway, if I am asking for more info, this means that I can't replicate the problem on my end or I don't know exactly how

This indicator is so slow, it even crashed my MT4. When I'm checking it's Buffer 1 it shows values like 0 or 0.00005. I don't know what they mean, but these values doesn't look to be prices. You can use Comment or Trace to see the values as well.

But what "bottom" and "top" means? I know some interesting meaning of "bottom", but...

Internet issues probably? What if you reload the page?

I am aware of these long numbers. i know this sucks and I don't know how to fix this entirely

If you are talking for block 5, I also always have Count = 1.0 and Total Profit is equal to Average Profit, but I think this is notmal because there is only 1 position at a time and it's total profit is also it's average profit.

The name of block 5 should be "Bucket of Positions", but remember that you are in MT5 which normally have 1 position and just recently it got this "hedging" thing. The Count here could be bigger than 1 only if you work with other positions from different symbols.

Again, this block is for the currently running position(s), not for closed positions that are in the history! For closed positions (or trades, or whatever you call them) you are actually using multiple "Bucket of Closed..." blocks.

Yes, each "Comment" block creates it's own individual space of letters and it's expected to see such overlapping.

But if you know something about this and you think that these news can be used for something, tell me. Because I normally don't see such news in my MetaTrader. I remember seeing them in the past, but I was confused by them. Whatever it is, it must have some kind of information that can be used by the EA. If it's only random text (for the EA), how can the EA understand it

keydcuk, when looking for crossover, 4 values are compared from 2 candles. 2 values from the chosen candle and 2 from the previous one. Well, it's the previous candle only if cross width is 1. If it's 10, then that previous candle is candle 10, not 1. So with this setting you can skip few candles. But note that they are really skipped, it's like they does not exists, they does not participate in the calculations. If you don't need that, don't change this cross width thing.

Indicator is visible now works the same as if you have the indicator in Condition. If one of the sides in Condition equals to EMPTY_VALUE, then the block does not pass. EMPTY_VALUE is the value that is used by indicators when their buffers must be not "visible".

Indicator moves within limits is the only* block that can look back in the history. All the other blocks are looking in particular candle or two candles when crossover is used.

• Only for custom indicators in Condition -> My Indicators you have some extra settings in More Settings. Some of them are looking for data back in the history.

There are 2 ways to deal with signals:

1. At the current moment look for data in the current or past candles and decide what to do. Do this on ever tick.
2. While the EA is working and you are searching for signals that must happen one after another in the time, you can use one or more Variables to keep the current stage of that searching in memory. On every tick check the value of that Variable and do something depending on that value.

I recently added some method of doing 2) without Variables. Look at this: https://fxdreema.com/demo/mt4-wait-crossovers But note that I still don't have reports from people using this method.

I have no idea how these news are used, to be honest