Posts made by fxDreema

For the built in fractals indicator use Candle ID of at least 2 (if I remember correctly)... or 3 if I'm wrong. It must be bigger than 0, because the fractal object appears on a previous candle, it never appears over/below the current one.

@Pipperoni Actually the "Trailing stop" block and the "Check profit" block are not internally connected in any way. When "Trailing stop" gets executed, it selects the trades by Group, by Market and by type, but this block doesn't care which block was above it at all. So I don't think that this will work.

Somewhere in the examples there is an example of how to make trailing stop with pink blocks. This means that you can get multiple pink blocks and make them do what the Trailing stop block does, but in addition you can do it differently - for example you can check what is the lot size of the currently selected trade. The downside is of course that all this is done my multiple blocks, not just one, it doesn't loop pretty in the project.

Strict mode is when you set the programming language to be more strict on the rules => it allows less freedom and shows more errors. So, in strict mode more errors are expected. As a result the code should be better. But in MQL4 for some reason it shows more errors in non-strict mode, which is strange for me I basically set this property only because I think that strict mode is good in general, but I'm confused by the actual results.

What can I say... maybe I will just remove that strict mode again. Every time I enable it, people start reporting those long numbers. Unfortunately sometimes even I don't know how to fix them. But in normal mode it's not that those numbers are not long, they only appear short when you print them, but in reality they are still long and inaccurate.

Buy now would not do this, because I didn't programmed it to do it (but it's not impossible in theory). You can find one block, something like "Set Market name for next blocks". If you put this one above Buy now, you will cause it to run multiple times, each time for different currency.
But remember that in MT4 you can't backtest this, it's not supported by the Tester. And because your EA will run on particular currency, the whole EA will depend on the ticks of that currency,

Don't worry about these. I said this again and again and again and again - warnings mean nothing (for you), they are not scary. What is important is for the block to work as expected.

I know much bigger messes, this project is still small and everything is ok.

It's not mandatory to give sequential numbers to the blocks. Those numbers are normally not important - in this project they are not important for sure. Only when you have parallel blocks - when one block is connected to multiple other blocks and there are multiple possible paths - only then blocks with lower number get executed first.

Once per tick - this block is not needed.

I tried this EA, but I quickly get out of money. You have too big lot sizes, something like 10 lots. I don't know, maybe you are trying this on a different symbol or with another parameters, but this is what I got - errors that say "Not enough money to trade"

You can obviously have indicator without any buffers. This is how its made, you can see that the code is full with "Object..." functions - so it doesn't use buffers, it creates objects on the chart. The normal way is to fill the buffers with data and then from the information in them MetaTrader decides what to draw, but in this case the indicator tells MetaTrader to draw objects.

Well, if I have to check your indicator, I would put it into a Trace blocks and I would start changing buffers and "Candle ID". Because sometimes indicators don't print their lines or arrows on the current candle, and you can see this when you try the indicator in Visual mode. So, when you try the buffers with different "Candle ID" you can find whether those buffers can give you something to work with, ot not. If there is nothing in the buffers... I don't know, maybe the indicator is just printing regular objects on the chart.

Only in the source code. FxDreema doesn't have that ability to set these options. This is otherwise interesting property, but I guess that I first need to do something, so that people can keep multiple versions from the same project in the same project. I was thinking about before actually. Right now you can do something like this in the History panel, but you can only save 1 history point from deletion, and it doesn't have version number.

I will take a look at this. If it works, simply skip these warnings.

Yes, I enabled strict mode, because with the new update I saw less warnings than expected. Before I was Not using strict mode mostly to hide bunch of warnings. But I guess there are still warnings here and there that needs to be cleared.

It's funny that now if you remove the strict mode, you will immediately see fatal error in OnInit(). This is strange

My first suggestion is to look at that Buy-Sell-Buy-Sell example in the examples, because this one shows that flip-flopping. Condition blocks will have something else in them, and I think that you also need to use "Once per bar" somewhere, to prevent something from happening 2 times in the came candle.

Or, maybe this block "Skip ticks". You are saying "stop the blocks from acting..." and this block does exactly that.

You are talking about the Open Price of the trades? You don't get this one from the objects, you get this from trades. I can say that you probably need to use "For each Trade" with some other pink blocks, but it depends. I mean, "For each Trade" is the block that can loop for each existing trade and select it (so you can get its values), but it's important which trades do you want to select, in what order, how many of them...

Candle ID should be at least 3 or something. 2 or 3, I don't remember exactly. The reason is that you never see fractal on the current candle, fractals appears on the chart few candles later.

Well, I always recommend to use Constants instead of these checkboxes. Checkboxes are fine, but I prefer them only for quick testing and then I uncheck them all. Unfortunately people use them too much

@nickmccomb I mean that in MQL4 we have some option for ObjectFind() - https://www.mql5.com/en/docs/objects/objectfind - you can see that chart_id parameter. But I'm not sure what they mean - chart or subwindow. I will test that later and if it works, I will add some option.

I think this is hard limit and cannot be increased. I remember that long time ago I was trying something with strings and I found this problem. I don't know how to increase this.

You found something for vertical lines, but you are asking for horizontal lines. Very strange And I don't understand why you want 100 horizontal lines.

Unfortunately this is not anomaly. Floating numbers work like that in those C languages. I don't understand why, I only know that it's normal. And that's why NormaliseDouble() exists - to normalize those weird numbers. But I also noticed that sometimes this function doesn't work, and I don't know what would work. Well, If I remove "#property strict", those weird numbers will appear like normal numbers, but I think that in general working in strict mode is better. Although the strict mode in MQL4 is crazy - if you remove it now, you will see fatal error. We are supposed to see more errors in strict mode, not in normal mode, but MQL4 is always a little bit broken.

I don't really understand the question. What is "over all in profit"?

The word "buffer" does not exist in this indicator