Posts made by fxDreema

But is it working with the levels? Because I think this is the way to do the job with the MQL functions. I probably tried to find a way to make it in the way you want and I probably failed. I don't remember very clearly, to be honest.

Yes, but not in Buy/Sell blocks. Remember - these blocks only do their job once when they are executed, they create their trade and that's all. Well, the only option that appears to continue working is the Expiration option for the MQL4 side.

https://fxdreema.com/demo/mt4-trailing-stop Trailing stop is an example how stops can be moved multiple times. And I would actually recommend this block for your task, if you also want stops to move only in one direction. You can see those Custom options for Trailing Stop.
If you want to modify stops every time, there is a block "Modify stops". Well, SL and TP are not separated in this block.
Or "For each Trade - > modify stops"

Draw Text. You can use the z-order options to make objects appear one in front of other.

Hiding indicator is possible in MT4, but not in MT5 I believe. There is no block to do that. I don't want to add functionality only for MT4 or MT5 alone. So the way is to use the MQL4 functions manually in "Custom MQL4 code"

Changing colors is not possible at all, as long as I know.

This cross width thing is probably cosmetic defect, not something fatal. That input field is always there, even if it's not visible.

I'm more afraid of that parameters change. The thing is that fxDreema become complex years ago and since then I'm only trying to make it simpler for me, to minimize potential problems when I decide to update something. But after all my efforts, bugs are still possible. Give me more details about this parameters change problem - what exactly happens and how can I cause the problem, so I can see it and fix it?

By the way, I discovered this problem minutes ago: https://fxdreema.com/forum/topic/4449/february-2017

This is true. I know that people who learn something very well eventually lose their ability to see from the newbie perspective. That's why most teachers are not very good teachers

In this case I will suggest to use 2 blocks for the 2 money managements. And some Constant that you can put into a Condition block above these blocks. Something like (ConstantName == Value->Boolean->True). I know that I'm recommending using more blocks right now, but this way you will be able to see what is happening in fxDreema (if you open the project in future) and also you can give good names to the input parameters.

@Didble-trader You can check the output code. But I never put anything intentionally to make the results different. Bugs are of course always possible, but it's important to say that some things are disabled in optimization - https://fxdreema.com/help/basics/testing-and-optimization-limits. Does the EA rely on chart objects?

Be careful with the first 2 options in "Draw..." blocks. Look here - https://fxdreema.com/help/working-with/chart-objects And also yesterday I added description for those 2 options, just click on their titles when they become yellow.

Maybe the indicator levels are not proper. Or you selected the wrong option? There is difference between "price level", "price fraction" and "pips". If you select the wrong one, you could see error... or fxDreema could try to correct that error and you will see wrong behavior. I think that you selected some option that resulted is small SL/TP, so the trades are closed early.

You see how ugly these input variables are anyway. I actually want to remove these checkboxes from the system, or hide them at least, because people are using them too much and I think this is a bad practice.

The whole idea is to develop the EA in fxDreema, not to make universal EA with tons of input settings. This is the reason I started fxDreema, because I found myself trying to make universal EA.

The problem is that you don't know the possible values of these pull down menus. Most of them have string values, some of them have numeric values. Depending on the time I made them and my mood at the time. Most of them have weird options that you will never guess, so that's why they are all disabled. And even if I make some enumerations for them (so they could appear as drop-down menus in the inputs of the EA) there will be a problem - in fxDreema when you change the value, some other parameters appear and disappear, but in MetaTrader this doesn't happen.

Even more - in the output file I have some optimizations to remove unnecessary code. When some parameters are hidden - they are not needed in the EA, so they can be removed. The idea is to put in the output code only the stuff you can clearly see in fxDreema.

And again, these are ugly looking. Their idea is much simpler than that. The idea is to select 2-3 checkboxes, to quickly try the EA with "Optimization" and then to uncheck them. To use good input parameters better use "Constants" - https://fxdreema.com/demo/mt4-constants

I see. I was updating many blocks these days, maybe something wrong happened. I will fix the problem right now

Well, if trades started to close immediately, this is at least something. People have this problem very often and the reason for that is because their conditions to buy/sell and the conditions to close trades are true at the same time. I don't know how to better explain the problem. It's not a bug in the problems, it's a logical error - the way blocks are connected.

Here is some example that contains very few blocks - https://fxdreema.com/demo/mt4-buy-sell-buy-sell-opposite-conditions - and at first you might think that something horrible will happen. But their settings and location are good.

Whatever you do, remember that all the blocks under "on Tick" run on every tick - over and over again, very quickly.

@tcanuto I have no idea how to do that. I was asking myself this question since the beginning, but I don't know any function to do that. Moving Average always appears red, but in iMA() there is no parameter for the color.

Or try those "Bucket" blocks... but they exist only in the web version
https://fxdreema.com/examples#Bucket-of...

Indicator can be invisible while backtesting (why do I think we wrote about this before). Basically there is a MQL4 function for that, but I haven't added it in any block, mostly because this same function doesn't exist in MQL5 and I want to keep both as equal as possible. I don't know khow to change indicator colors from the EA.

I can see you are using those checkboxes to make parameters inputs for the EA. First of all, I really don't recommend to use these. And what is the problem.... when you modify input parameters once in MT, then they are saved somewhere in a cache file. You can modify the default value of the parameter in MetaEditor and there will be no difference. Only if you delete the cache file MetaTrader will start to see the new default values.

https://fxdreema.com/demo/mt4-buy-sell-buy-sell-opposite-conditions

@tcanuto What? You can change everything inside the file of the indicator.

There is a way for everything... but the way is sometimes longer

I don't understand the question very much. Block "Buy now" makes a new trade every time it runs. It doesn't care of which candle it is, what time it is... only cares about how much money there are

Block like "Close trades" (if you use it) also does its job. So be careful when you use such blocks. Many people are asking me why they see multiple trades opening and closing again and again. Do not allow blocks like "Close trades" to run at the same time as "Buy now".

No, there is no expiration mode that will wait for certain candle to be opened. My idea was that you can set some time. And this time can also be calculated according to the current timeframe. There is a function that returns the current period - Period(). And if the period is M15, it will return 15 (which is the value of PERIOD_M15)

Your file works now