Posts made by fxDreema

I got lost somewhere in the middle of the first sentence But I feel that you are asking for something like this (I answered to this topic just before yours) https://fxdreema.com/forum/topic/5285/set-same-tp-and-sl-every-entry

I guess by looking at SL and TP of the previously closed trade, something similar to this: http://prntscr.com/hag7gg

Or you can define 2 variables - one for SL and one for TP, use them in the Buy/Sell block, and modify them only when you want to change the SL and TP levels.

No. You can only import .mq4 files previously created by fxDreema. This is because there is embedded data about the project in the .mq4 file (at the bottom of the file) that fxDreema adds automatically. When importing a file, the MQL4 code is never read.

You know, I don't recommend using this block and also the blocks around this one who have crazy names. I made this block long time ago when I was thinking that "I should create as many blocks as possible". In reality, what this block tries to do is better to be done with a custom indicator. I basically created just a single custom indicator with this block, which is not a real custom indicator.

I also kinda forgot what the values mean in this block. This block should detect when the current bar is much bigger than the previous bars, so "quiet" bars are those small bars that are supposed to exist before the current big bar. And "min size" is a filter that tells that each of these small bars must be at least 10 pips (this is the default value). This is because sometimes bars are much smaller and the detected "impulse" bar is actually not so big.

Impulse shift is when you want to look at the previous bar, or some previous bar. Instead of looking at the current bar, look at some of the already closed bars. Nothing special.

I will be better if you give the actual indicator. Custom indicators are not uploaded to the server

But again, you must know what's inside the output buffers of the indicator you are using. For example "Indicator rise" can be used for MA, but your indicator is not MA, even if looks like MA.

If the indicator has 2 output buffers, one for the red line and one for the green line, and those lines alternate (when the green line stops, the red line starts), then this most probably means that while one of the lines is visible, the other line is invisible and its value equals to EMPTY_VALUE. So you can try "Indicator appear", which is designed to the moment when the value goes from EMPTY_VALUE to some normal value like the current price.

"Indicator rise" is to look at the values in few candles, compare those values and decide whether they are growing or not.

Round numbers detector is some kind of filter, it should be placed somewhere under "on Tick" so it can check the current price at every tick and it would pass every time the price reaches a new round number. But this block is not really suitable for making pending orders.

In the pending orders blocks there is nothing about round numbers, this is something that I should add, but who knows when. Anyway, I got something for you. These are some simple formulas for calculating round numbers out of the Bid price (in this example): https://fxdreema.com/shared/xHE9eHHHc

MathCeil() and MathFloor() are MQL4 functions that give you the nearest bigger and the nearest smaller integer:
https://www.mql5.com/en/docs/standardlibrary/mathematics/stat/mathsubfunctions/statmathceil
https://www.mql5.com/en/docs/standardlibrary/mathematics/stat/mathsubfunctions/statmathfloor

Bid is a predefined variable in MQL4 and it gives you the current Bid price of course. There is Ask as well.

My example gives this result on the chart: http://prntscr.com/hafr46

These values can be used as Open Price for a pending order and you can also customize the formula if you want.

In fxDreema I only added those indicators that are available in MetaTrader, in particular MQL4/5. Plus modified version of ZigZag (I hate this indicator) and HeikenAshi, which are both .mq4/.mq5 example indicators that come with MetaTrader, so they are technically also built in indicators.

It can be done in an EA, but I think this is better to be done as an Indicator, because this is what Indicators do

I have no idea, there is no such price But I tend to think that these prices are cheap in the world of Forex.

In one hand this is just a piece of software, similar to many other paid or free softwares, so how much should it cost really?
And in the other hand, this is the Forex world where I remember seeing $19 or more dollars at loss when I tried my trading skills, many many times.

If what you want is an expiration, there are expiration settings in "Buy now" and "Sell now" blocks. Remember, for this to work the EA should work as well, because this expiration does not happen on the server.

Or if you want to close trades at certain time each day, just connect "Close trades" after "Once a day"

What do you mean to extend the profit?

The same old issue again...

Custom indicators have output buffers, which are arrays of data - 1 value for each candle. The EA is supposed to work with that information, the EA does not "see" colors, it sees numbers. What are custom indicators actually? They are code that fills those arrays with data and they also have some rules of how to display that data on the chart, so it can look as line, histogram, arrows or whatever. Again, there is 1 value for each candle in each output buffer.

Use "Trace" to see what is inside the buffer you want to check: https://fxdreema.com/demo/mt4-trace-multiple
When you see that you have some meaningful information, you can use the indicator properly.

Maybe your indicator has one output buffer for each line that has different color. So, if the value at certain candle is for example 1.2345, the line is drawn there. To be invisible, the value is EMPTY_VALUE (which is some big big number, the biggest int number).

If this is the case and one line has values either EMPTY_VALUE or price values, try "Indicator appear" to detect the appearance of the line or "Indicator is visible" to detect if there is a line at the chosen candle. Well, I normally use Condition (indicator > 0) instead of "Indicator is visible", because it is supposed to work faster (it works because if either value in the Condition block equals to EMPTY_VALUE, the block won't pass).

There is a block "Bulls in a row" that can be used to detect those 3 candles and you can compare different values in two candles in the Condition block

I looked before, but I did something wrong and I activated it for another person So now I gave you 1 extra month. Meanwhile you paid for another 12 months, for which I thank you very much. With the other 4 months you are probably the one with the longest period now

I also don't know much about licensing, but what you can try is to put some "Condition" block in "on Init" to check something... password, login or whatever... and after that block you can put "Terminate" to close the EA. Also, put some block to print information, so the person knows what is going on.

You can also try this: http://prntscr.com/h6oczi - but obviously this requires certain date to be entered, and the clock of the PC can be changed

You want to create and EA to do this or you are asking for this to be available for all EAs that are generated?

I don't know how to check for withdrawal the native way. There is a function to make withdrawal - https://www.mql5.com/en/docs/common/testerwithdrawal. But how to detect real withdrawal... I don't really know.

I also think that it's better to have some Condition block that checks whether some Variable equals to true/false or 1/0... or something else.

If you have fully disconnected blocks, they are excluded from the output file. In your case this will happen, I believe. The EA generator does not check the contents of the Run block. And so many blocks to turn on/off... I think it's too much and you are doing something in the worse way.

Just in case, if you have a group of blocks and you want to prevent that group of blocks to work, it's enough to turn off only the block on the top (if there is only 1 block on the top). If the block on the top doesn't have the chance to pass, then the blocks below will never pass, even if they are not disabled.

Yes, you can write MQL4 code in all input fields, you can use native MQL4 functions in them and so on. In this case you have "stopLoss" and "delta" as a variables and they must be declared as variables in Variables (the same way you declared "tsl")

I don't really understand your question