Posts made by fxDreema

With default settings it is working, I can't say what is wrong when I don't know what settings you are using. Maybe "Dynamic" one... from what can I see, the value in this case goes directly, it is price level, not a pips value, so what you write is what it will be exactly. And it's true that I need to update this block... or remove it

The same can be done with some pink blocks: https://fxdreema.com/shared/FgGUhSP8b
For MT5 even "modify stops" (without For each Position) can be enough, if the EA works with the current market only.

Wow, this was old and dangerous bug, I wonder how it was not reported long ago
I think I fixed it, it was only for some MM ("Risk" ones) and only for pending orders. At some place in the code I was using ask/bid instead of the open price, and this caused wrong calculations for the lot size.

You can try it now, is it ok?

I uploaded 084 again, is it now ok?

Damn I'm sure it worked for the web version...

open-to-close price is the difference between Open Price and Close Price when the trade was closed, so you should use "For each Closed Trade" here. Otherwise I think that Close Price is the current price, if not 0 (I don't remember exactly).

Both prices are the real prices where the trade opened and closed, so the spread is probably somewhere in there. Well, not the current spread, but the one that was in those events.

The spread is available somewhere else in Condition, somewhere under Market properties again as price fraction (ask - bid). Otherwise as MQL4 code it is:

MarketInfo(Symbol(), MODE_ASK) - MarketInfo(Symbol(), MODE_BID)

But do you really need that...

There is something else, but this returns points which are probably not really useful in fxDreema. If the spread is 2 pips, it will return 20 Again, if I remember correctly

MarketInfo(Symbol(), MODE_SPREAD)

Fractal indicator? (by the way it has delay of 2 candles if I remember correctly)

Well, I updated the web version. Additionally, I reuploaded the local version with this fix, but my updates does not affect older local versions that somebody have... the local version has it's own local database

Pips away from TP - means, that it detects when the price is at some distance from TP. For Buys, this is when the price moves down at some distance from TP. The current price for Buys is used to be Ask, so the formula you show obviously operates with Buys. Then when we do TP-Ask, because TP is above ask, the result will be positive and we are serching for that. The opposite Ask-TP will be negative and... not the one we are searching for, because on the other side we probably have positive value (if PipsAway is positive).

Get the local version that I reuploaded or try it on the web. At least I can see what are you doing on the web.

My fault, it must be fixed

I added this option. But if you work with multiple trades at a time, 1 flag will not work correctly. So I added another option for the ticket number: http://prntscr.com/3qgq2e
Also for the "(on trade)..." part in Condition. The parent ticket is the one that belongs to the trade before it was partially closed, or this is the regular ticket number when it was still untouched.

The next build is up already

I updated this block a little bit, to not pass if there is no TP on the trade or if there is no SL when % of SL is used, but otherwise I think that it's working correctly. What is the exact situation that you have, some simple example, screenshot, something?

I fixed it for you, now there are no errors.

There are some parameters that already accept value that is measured in "pips", like this "Price offset" parameter. There is no reason to write the word "pips" because whatever number you write, it is considered as pips: http://prntscr.com/3q8yrj And yes, you can use positive or negative value for this parameter.

Aaaaah translators...
In short, the value above must be bigger than the value below.

Look at the blocks 75 and 78. "Different pips", what do you mean by that?

I think it's fixed (reload the browser). The default values there are:

0.001 = 0.01
0.00001 = 0.0001
0.000001 = 0.0001

You can use "-5pips" in "Adjust" fields, but this does not work in other fields... like those like "Price offset" that accepts pips value anyway. Use only "5" or "-5" here: http://prntscr.com/3q6pl3

Oops, the other problem seems to be serious, I will check it right now.

Here are some reasons to not load the indicator properly:

• The indicator is not there. Now you can run MT in normal mode or portable mode, and files are on different locations in both cases. Go to "File - Open Data Folder" to see where are your files.
• The indicator (if you don't have the source) is on the right place, but compiled under older MT version
• Input parameters are not correct. This is where fxDreema can be wrong. I found some problem with is before and I think I fixed it, but who knows... Just check if your indicator has the same count of input parameters as the count that fxDreema recognizes. Also datatypes are important.

For the BE. Pips on profit is where it will lock the SL. By default it will place it on the Open Price (SL = OP), but optionally you can use this Break Even Point Offset parameter to place SL at OP + PipsOffset. Think of BEP (break even point) as the level where SL is, where the loss should be 0 (or not exactly 0 when there is some commission and/or swap).
And yes, obviously I have to fix some parameter names because it is confusing. I have to apologize for that.

Mine appears, I compiled that indicator and I have it's .ex5 on the right place: http://prntscr.com/3pxhaa

But I can see problems with BE. The offset (2.5 pip) - where to put SL in relation to the open price - is bigger than the profit (1 pip) that the position needs to reach. So it tries to put SL at 2.5 pips below [above for buy] the open price when the price is only 1 pip below the open price.

Block titles does not depends on the block type. The local version is a little bit more problematic What actions do you do to make the problem happen?

It's not only HH:MM, the function StrToTime is used, which allows different variants: http://docs.mql4.com/convert/strtotime
But I don't think you need other variants, because they are too specific with their day, month and year, while HH:MM is for the current day. This HH:MM is not the number of seconds, it does not return 1800 when it is 00:30. What it returns is the unix timestamp at 00:30 for the current day.
Adding some time is normally done by adding seconds, for example in the "Adjust" field, something like "+1800" (if the value above is time value of course). There is no "Adjust" for Value-Time, but there is this "Shift in Time", which is basically the same.