Posts made by fxDreema

Just don't use this strict mode. If I have to fix all these warnings and errors... who knows, maybe I will break some functionality here and there. For examle, there is one parameter called "Group #", which is always a numeric value and should be "int", but I changed it to "string" so people can use values like 1,2,3,4 to select multiple Group numbers for the same block. When string with value of "1" is used somewhere in the code as numeric value, MQL4 translates it into 1, but in strict mode it will print warning. I can't stop MetaEditor from throwing these warnings, but I will not break this functionslity (and others) only because some warnings

I'm sure that there are warnings and even errors in strict mode MQL4 is limited language and becomes stupidly limited in strict mode in my opinion.

Well, I have problems to make it possible to browse for folders in the browser

What are your settings now?

Directly over the variable. If the variable is called MyVar and has a value of -10, then MathAbs(MyVar) gives you 10.

There are no conversion blocks in fxDreema, as you can see. I mean, blocks where you can select a Variable from a list and then from another list to select "Absolute value". I think that these conversions can be done easily by writing them as native MQL4 code.

I'm sure that in the same group of candles their Highest point is always different than their Lowest point and more than that - the Highest point is also always above the Lowest pont.

So I'm not sure that you really want to compare those two prices like that. If you want to just put a pending order at some level, select this level in it's block. Something like this: http://prntscr.com/977cv5

And what is wrong in the screenshot? From what I can see, all conditions are working fine The newest candle is the opposite type and inside the previous candle.

There are some native math functions: https://www.mql5.com/en/docs/math

Oops, my fault! It must be fixed now

And what is the problem?

By the way in blocks 6 and 7 you are working with candles 0 and 1, while in all other blocks you work with 1 and 2.

https://www.mql5.com/en/docs/convert/normalizedouble

Something like trailing stop, but for TP? In the block for trailing stop you can select to trail TP instead of SL

These are nowhere used in the builder, but if you have some code that can be put into a function, then maybe. Everyone can create custom blocks and functions.

I give up here I was never interested in writing indicators and I also truly hate this Zig Zag thing

http://prntscr.com/94xp6b
http://i.imgur.com/duj8dRj.png

Those buffers are giving signals in the beginning of a new day and at that time I think the indicator is recalculated. By signals I mean values of 0, but I can't see how this can be used.

When I use default settings I see it like this: http://prntscr.com/94co9o I have no idea how this indicator works.

Rectangles have names like "SSSR#12 Strength=Verified, Test Count=1". If you think that you can use them... use them. I already said how you can give Price 1 and Price 2. Again, I am talking for these prices - http://prntscr.com/94comz - because rectangles are built from 2 prices and 2 times.

"For each Object" can filter objects by name as well: http://prntscr.com/94coz5 But what to write there... I don't know.

Damn, this sure fire again. Long time ago I made this example https://fxdreema.com/shared/rShdtBC4e, but if you ask me, I don't like those "hedging" strategies and I believe that these are only a way to make Martingale in much more complex way. Such EA does what Martingale does, but it's much harder to build and maintain, at least. It's much easier to play with Martingale and yes, stops.

But this is the idea of Trailing stop, to move SL. This is what I got - http://prntscr.com/94b7x8 - it looks as I expected. But you have Step as 0, which is ok for the EA, but it results in many modifications and brokers don't like such behavious, so I will recommend to have some Step.

Otherwise I explained the logic behind this block.

If these rectangles are made by indicator, of course, first try to see what it's buffers can give you as signals. It's possible that you have access to the data you need exactly. I was talking in the case when the only way is to get some information out of the objects.

Indicator is visible - this detects if some buffer is different than EMPTY_VALUE or 0. Basically it's the same if you use "Condition" to compare indicator with > 0. If one of the sides in "Condition" is "EMPTY_VALUE", it does not pass.

Example of how to use "Comment"? Just put this "Comment" block somewhere and fill it with some data. In order to see the data of any "Data row", fill in the "Label". If there is no Label, that row will not be printed.

This type of object is built from 2 points, each one with price and time - http://docs.mql4.com/constants/objectco ... _rectangle

The closest to the price is most probably a object with name that is also closest to Z. As you know, objects are selected by their name and "For each Object" searches for objects from A to Z or from Z to A. Finding the first pink rectangle with Z-A sorting sounds to me like it will do the job. For this, set "Not more than..." to 1.

Of course it is possible that A-Z will work better, just check the names of those objects to decide how to sort them.

I will suggest to first play a little bit with "Indicator tester", until you get the idea and until you understand Price 1 and Price 2.