Best posts made by fxDreema

Ok, now it looks that it's working

No. I personally don't like any form of advertising, I don't understand it and I just can't think of this

Yes, I posted two sample files above. It's ok to write all the parameters, name the file as the name of the indicator and upload it to fxDreema. Also you have to put the number of buffers and optionally give them names. This is not so different as if there is an option to manually create list of parameters directly in fxDreema.

Sometimes there are extensions in the browser that prevent some of the .js scripts. I don't know exactly why. I wrote pretty much all .js files used in fxDreema and they generally work, but there are extensions that for some reason don't like something in the code.

The last situation - some Norton extension prevented one of my scripts saying that some frames are not allowed... but when I look into the code I don't see any frames (iframe or something related). So even I am confused

Sorry, I don't work as a personal programmer and I don't want to. Well, you can always find one over the internet. I also don't care about anyone's strategies, but I'm here to support fxDreema itself and to answer questions about how to work with it.

I know it's not easy sometimes, because in order to create a strategy, you must build it logically, after all this is a program and it does what the programmer tells it to do in appropriate language. Here - in the language of some blocks and variables. So, no MQL needed, but the language of logic is mandatory.

I can recommend you to open MetaEditor and start learning MQL4. I think you have time to do that, and I'm sure it will boost your knowledge and potential. And it's also fun. You will not be the next great programmer, but it's good just to understand basics, to feel the EAs, and this can happen for about 1 month I believe.

I will check this block. I made some updates on many blocks lately, maybe I added some bug... or it was there for a long time

Group number is part of Magic number (Magic number = Magic start (found in input options) + Group) and if you will complicate the project... I don't recomment complications. At least everything that I'm trying to do is to simplify things.

If you want to differentiate trades by symbol, use in trading blocks (such as "On trade is running") "Specific market" option, not "Any market".

Fixed. I copied some code from my local fxDreema, but I didn't noticed that the names of some parameters were different. I renamed those parameters in my local version and eventually I will rename them in the web version

There are no conversion blocks, but the native MQL4 functions are not hard to use:
http://docs.mql4.com/math/mathabs

MathAbs(3-5) should give you 2.

So I got few emails with the same problem - some blocks are missing and the project appears to be empty. I don't know why that happened, I was out of town and I didn't uploaded any updates in more than a week. Few days ago the website was very slow for some reason and I just restarted it. Maybe this explain those missing blocks somehow, but I honestly don't know why the website was slow It was working good since then.

Here is a quick hint for how to "fix" missing blocks - just go to that "History" link in the upper right corner and go to some previous history point that works. Also, every time you export .mq4 or .mq5 file, the project itself is embedded in the end of that file, so the project can be imported back into fxDreema at any time (or at least when the website is working normally :))).

By the way these days I will move the website to another VPS. New VPS - New problems Well, I actually hope that after that it will work a little bit better, at least I will have 1GB of RAM more.

10 pips grid which is updated on every 10 pips? Why do I think that only the first (virtual or not) pending order in that grid will be used

There is a block "Round numbers detector" which passes on every few pips - one of it's outputs is active at a time, depending on the price movement (up or down). It goes up 10 pips - orange out is active. It goes down with 10 pips -the yellow one is active. Up, Down, Up, Up - orange, yellow, orange, orange.
If you connect some "Buy/Sell now" blocks to this block, isn't this similar to what you want?

Take a look at the documentation about NormalizeDouble - https://www.mql5.com/en/docs/convert/normalizedouble

What they say is this:

Please note that when output to Journal using the Print() function, a normalized number may contain a greater number of decimal places than you expect.

There is no guarantee about these numbers. I tried everything, but still sometimes numbers appear long, even after NormalizeDouble or DoubleToString.

You tried that Trailing stop? It's not only what it sounds like, it can follow the ATR levels or the levels of any similar indicator. As a result SL is placed at the newest ATR level. I think you are trying to make it the hard way. Yes, normally the Trailing stop block moves SL at fixed pips distance, but this block is one of these with many options. It can also trail TP, which sounds the opposite of Trailing Stop.

I don't know, I have this: http://prntscr.com/4em4c5
Some trades are opened at some levels and I don't even see how they can close. Also I think that Martingale should be used when there are no trades opened, which is not the case here. Now it gets lot size from the last opened trade, I enabled this because some people wanted it, and this is... I don't know, I can't get it.

Please, learn one simple thing. When you want to add something new to the project, try the new thing in another EA, only the thing, as simple as possible, with only few blocks. Then if it does not work you will know it and you will be sure where is the problem. Because now... you are adding something new over something complex and then you try it... things are getting more and more complex and hard to debug. I believe In this case you are going nowhere

By the way, define "jumping lot size". I can see you have added fixed lots on loss, which turns Martingale into something that is called Grand Martingale. If you don't realize that you may think that these 0.01 are something else... initial or something.

It's not because of the size. There is an error in the update script and I need to check why it happens. I guess that you made this on the desktop version where the project's format is... old. The web version tries to update each project to the newest format, but at some point it fails.

Edit: I found the problem, I had some undefined variable in JS code By he way 218 blocks is not huge, I know projects with thousands of blocks

I just added new mode in Trailing stop (each trade), MQL4 only, web version. I marked it as experimental because I'm not sure about it. You can test it and then tell me if it's ok and what should be different.

How it works... you write levels like this:

20/5, 30/10, 45/15

.. which means that when the profit reaches 20 pips, SL will be set to 5 pips (from the Open Price, not from the current price!), at 30 pips of profit SL will be set to 10 and so on...

It's also important to write groups in order starting from the minimum value. 20 first, then 30, then 40... But not 20, 40, 30. This is because MQL4 is very unfriendly when arrays are used and I don't want to add more calculations for sorting.

"Step" is still working. By default it is 1, so we actually have 21/5, 31/10, 46/15. I can exclude it from this mode and set it to always be 0, but... I don't know, people always want more options.

What I don't like in this way is that all numeric values are written in a single string, which means that it will be very ugly if someone wants to use some variable instead. That's why I marked it as experimental.

Otherwise similar functionality can be made using multiple pink blocks. Something like:
For each trade -> pips away from open price -> once per trade/order -> modify stops
but not only this, there must be multiple "pips away from open price" blocks and they must be ordered starting from the biggest profit. Yes, this is also ugly.

I will take a look. I just uploaded some updates and this is most likely the reason.

MQL functions can be used everywhere, all input fuelds in all blocks accept MQL code. The problem is that MathAbs() accepts input parameter between ( and ) and this parameter must be also written manually. If Variable is used it will not look as the blue thing. It will look like this: http://prntscr.com/9f2sil

I think I fixed this

The one from which you want to get absolute value

I have some ideas from where this problem can come, but it can be hard for me to easily fix it, because I have some ugly code there that needs extra care. The problem is that "Shift" parameter is already the actual name of the "Candle ID" parameter and there is a collision. It would be the same if you have parameter "Period". But I can tell you how to escape the problem - just rename the input parameter to something else. Parameter names of custom indicators doesn't really matter that much.