Posts made by fxDreema

"Comment" block is capable of automatically printing the time in human-readable format, but it includes also day, month and year.
In "Condition" where you can get the time, it is in this epoch format because only in this format the time can be used for calculations.
There is no place where the time can be get as a string and it's not because it is hard to do that.

This is the function to convert the time to string: http://docs.mql4.com/convert/timetostring

For example:
TimeToString(TimeLocal(), TIME_MINUTES);
https://fxdreema.com/shared/0vowJSKZ

https://fxdreema.com/shared/X4hFHV7Qc
http://prntscr.com/8khxc3

I have no idea to be honest, I never tested this function and I'm not even 100% sure if this is the right function

Which project is this? I tested your newest 3 projects and they can be compiled.

I did the trick and now it should wotk for MT4. I mean, Weekly and Monthly timeframe should work for Candle properties in the Tester. I found that everything is fine in MT5. If something is still not working for you, then I think I don't understand your request, so give me some project or screenshot

I added GMT options, I hope I didn't missed some block

It would be some trick, but I think it's my job to make it, so I will try it later

You reminded me that I have this in my To Do list, so I will add this option in the blocks. Also if you want to use this time directly, the MQL function for this is http://docs.mql4.com/dateandtime/timegmt

It is possible, but from the source code. I think it was a function called "DrawSpreadInfo".

Expert advisor name... I don't think that this can be controlled, the smiley face just appears on the upper right corner because of MetaTrader itself.

This is for trades only, not pending orders. The problem comes from the fact that we send the request of our future trade in absolute values - SL and TP values are absolute, like 1.23456, not relative values to the open price, like 0.0010. Then on the server the Open Price can be something different than what we wanted, but SL and TP will be the absolute values we have sent. So eventually our Open Price will shift towards SL or TP.

In the EA I decided this - when such thing happens, to modify SL and TP relative to the open price. For this, the EA just compares the Open Price we initially wanted with the real Open Price at which the trade was opened. If there is a difference between those two prices - SL and TP are modified immediately. But pending orders are not monitored for this. It can be done, I guess, but now this only works for trades.

My idea is... isn't the server responsible to open pending orders at the price we want? There is no reason for big slippage, because there is no network delay of the request. The pending order exists on the server and the server is responsble to open it on the correct price. The server have the most fresh quotes. 30 pips difference.... I don't know, is this because the market was really really weird at that time or it was some bug from the broker?

Select another EA and then return to the one you want to optimize, this will refresh the input parameters when you click on "Expert Properties".

If the current candle is from the Daily timeframe, it's Open price will be the real open price at ~ 00:00. The same for weekly and montly timeframes, but note that these will probably not work on backtesting.

I have no ideas to do something more for these blocks (MACD Divergence), I was actually thinking to hide them. That's because these blocks do what a custom indicator is supposed to do. I created them looong time ago because I wanted interesting options in the builder, but then I realized that I'm trying to do what a custom indicator should do. And we know that there are maaaaany indicators out there with maaaaany features. I just don't want to keep adding unlimited number of features for these stupid blocks. Even now they are pretty complex inside.

For the EA you have, I think you can connect blocks one-after-another more. "AND" is not needed, just connect 65, 1 and 2 one after another. At the bottom below block 20 it is similar. Now you have blocks connected in parallel there, but in this case their number matters. Just connect them one after another, which will also produce predictable results.

This looks complex Now every "Draw..." block is like a MQL function that looks as a block. All the possible input arguments are there + the ability of the block to create/update what it created in 4 different ways, depending on the two settings at the top.

You want to create multiple objects using the same block and then to keep them updated. I was not thinking about that before, but it should happen by using some loops and variables of course. I'm not sure if using blocks is better in this situation. In the same time writing code to work with objects is really... so many functions are used for every little detail. I noticed that there are libraries to do some things easily, but I never tried them.

This is ugly. I have an idea what could be wrong and it will be fixed withing minutes.

I think I tried such indicator long time ago and it didn't worked. Maybe these indicators are for manual trading only, I don't know. And yes, negative candles are also possible sometimes, for example in Ichimoku Kinko Hyo. But if no Candle ID works for this indicator... well, maybe it's not built in a way to work like this

The closing time is easy, somewhere in Condition - (in loop)... or directly with OrderCloseTime(). But this is unix format - the number of seconds since 1.1.1970 http://www.epochconverter.com/

But why don't you create those trades directly in this chart

Try with different Candle ID

There is pink block "check age", otherwise I would not use Formula blocks, directly using this value in Condition should be enough