Check profit (period of time) check the profit made from closed positions. To check the profit from currently running position, try Check profit (unrealized)
Posts made by fxDreema
-
RE: stop-loss with double the current positionposted in Questions & Answers
-
RE: input variables of indicators w/ multiple choice to be selectableposted in Questions & Answers
Try it. I expect this to work
-
RE: input variables of indicators w/ multiple choice to be selectableposted in Questions & Answers
When you create new Constant or Variable, you can put custm data type - double, int, bool... or ENUM_%whatever%
-
RE: Stop ATRposted in Questions & Answers
There is no block to do that or any other calculations with multiple values. Here is something that is not very pretty, but it does the job - https://fxdreema.com/shared/XAQKWPure
First, I put al values into an array and then I used this function to get the maximum value from that array - https://www.mql5.com/en/docs/array/arraymaximum
The syntax is not very beautiful, but we don't have many freedom with arrays in MQL4/MQL5. I tried this: double array[3] = {Value1, Value2, Value3), but it didn't worked... -
RE: Project variables are getting resetposted in Questions & Answers
Well, I'm also not very good in calculations
If your deposit is in USD and you work on EURUSD, then the amount of money per pip is fixed. But if you cross symbols, then it's a little bit weird. Somewhere in Condition -> Market Propertied there is option "Money per tick". I think this one can be used for these calculations. But how... :))) -
RE: Custom Price Level - is this a bug?posted in Bug Reports
So you have slippage. I programmed the EAs in a way, so if slippage happens, to modify SL/TP after that. The idea is that if you want SL to be 100 pips from the open price, it's going to be 100 pips from the open price, even if the open price happens to be different that the price that was requested. If this happened, you would be able to see "modify" immediately after the trade is created.
-
RE: Trace functionposted in Questions & Answers
No, I did nothing. This works for me, I see some lines. Of course numbers on the right side overlap, but I see lines
-
RE: How to separate the last 2 real digitsposted in Questions & Answers
This equals to 26
(1.4126100 - MathFloor(1.4126100))*100
Maybe it can be simplified.. I'm not that good in mathematics

I tried to use the % operator, but I gor error in MQL4
-
RE: How to delete a pending order after x seconds... preciselyposted in Questions & Answers
I would try this: For each Pending Order -> check age -> close
But remember that if you work under "on Tick", then you will not always get a tick coming exactly 10 seconds after the order. They come when they want, they don't care about time. So if you want precise time, you need to work under "on Timer". It's period can be set from the project settings (the bench icon). But note that "on Timer" does not work in the Tester, because the Tester works with it's generated ticks
-
RE: How to check the position order number >2 to stop the transactionposted in Questions & Answers
By "transaction" you mean what? If you want to check how many trades exists at the moment, try "Check trades count"
-
RE: Custom Price Level - is this a bug?posted in Bug Reports
I don't see dax30 in my symbols, so I tried this on Gold and this is what I got - http://prntscr.com/bgedtb I don't know how to get that problem

-
RE: Flicker on x>posted in Questions & Answers
If you have something like this - https://fxdreema.com/shared/w5Pxyrjve - then this is what happens.
- When the condition is true, a new Buy trade is created
- Now "If trade" is able to pass, because of that Buy trade that already exists. So it passes.
- What follows is "Once per bar". This block has internal memory and knows that it was already called in the current bar. But this is the first time that this particular "Once per bar" is called, so it passes immediately
- The next block is "Close trades" and the Buy trade closes
Note that "Once per bar" is working on individual level. Each one of these blocks has its own internal memory. You can call "Once per bar" block in the beginning of the bar or in the middle, it doesn't matter, it will pass once at the time its called. Here is more: https://fxdreema.com/demo/mt4-once-per-bar
-
RE: Take Profit using ATRposted in Questions & Answers
It can be used. Yes, this Adjust field is a bit different, but you can still write names of Constants, Variables, even MQL4/MQL5 code (functions and everything)
-
RE: Take Profit using ATRposted in Questions & Answers
For TP you can select something like Custom (price fraction) and select ATR. By price fraction I mean values like those from ATR. To double the value of ATR put *2 in it's Adjust field.
-
RE: Pause the EA when reached targhet and go again.posted in Questions & Answers
Terminate also closes the EA!
My idea about the Check profit blocks is that you can check the profit in a period of time and NOT doing something else. Because the block checks the profit in a period of time, that period eventually ends and the block will then detect 0 profits
-
RE: Flicker on x>posted in Questions & Answers
When trade is opened and then immediately closed, this means that the condition to open it and the condition to close it are both true, they both pass one after another
-
RE: Locking problem in visual testposted in Questions & Answers
Now there are more that 9000 registrations, yours is 1726. Not really from the first people, but 2013 was 3 years ago

I will start paying to people to give me simple projects with 2-3 blocks to show me the problem

-
RE: lower highs and higher lowsposted in Questions & Answers
I don't even want to add such indicator-like stuff in the EA builder. Things like this is job for indicators. By the way you can try the Zig-Zag indicator that is on the bottom of the built-in indicators. There are some HH and LL options over there. I don't remember what I did, but you can use Trace to see the values.
-
RE: Newbie Problems? Help pleaseposted in Bug Reports
Here I tried to explain the problem with Bar Close - https://fxdreema.com/help/-/working%20w ... e%20closes
Many people asked for this. Yes, it seems something very logical. But in reality you never know which will be the last tick in the current bar. The EA is working based on ticks, so anything happens only if tick comes.
Everything would work if instead of ticks, the EA works on clock. Like, check for new tick on every 1 millisecond. Only in this way you can detect the final millisecond of the bar. And in theory the EA can be made to work this way with endless while loop, but the Tester can't work that way. If you have endless while loop, the Tester simply hangs in the very first tick and no other ticks are received.