Posts made by fxDreema

To detect points, let's say 1 and 2, you know... there are indicators and candles or a combination of them. There are multiple ways of doing this - someone may use stoch, other can use MA, two MAs, PSAR, something else. But when you know what should be calculated, "Condition" block(s) are used basically.

Trend is detected mostly with MA or two MAs. When a single MA is rising (lower in older bar) or when the faster MA is above the slower one... you know.

In "Buy pending order" there is an option to put the order on certain level - Dynamic level. Whether it will be stop or limit order depends on where is the open price in relation to the current price, so there is no option to select "Stop/Limit". You can put that order somewhere with open price, sl and tp calculated on that moment, and you can also put the order and then move it depending on the market movement (this will probably require to create a loop - pink blocks).

Now the question is how will you know these points and when are they calculated.

I don't know. Skipping this error, Is it working at all?

Yes, those blocks are for managing the number of trades, and because many people use them I think there are no problems with them at the moment. Maybe you can tell me the name of your project so I can check it? I can see you have many and I'm not sure which one to look at...

In any case it's better if the indicator gives proper signals to it's buffers, but objects can be used too.

Остави спред филтъра, нали става въпрос за блоковете за време, а те се тестват като им закачиш един "Draw arrow" и гледаш дали в тоя период има начертани купища стрелкички. Надолу нещата вече зависят от налични поръчки, и поне аз не съм ги разглеждал обстойно... щото ставаше въпрос за времената.

На блоковете е зададено сървърно време, което при тестване е все едно. И пак тествах - работи си. Не знам какво, ама сигурно изпускаш нещо. Иначе при странни и трудно обясними ситуации за по-бързо и по-лесно ползвам TeamViewer...

На мен май ми бачкат всеки път, не че съм проверявал с години назад де... Да няма липсващи барове нещо?

Има си моменти в които и другите работят. Сложи един "Draw arrow" след който и да е и то ще ти покаже кога пропускат.

Because there is nothing for "Time" in Condition, but you can try to put this function in Value (numeric)... I think it's possible to
work.

Can you check this project for missing blocks or connections? There is some problem with blocks 53, 54 and 61, but I can't see 53 and 54, maybe there are deleted before but some wrong information is located in the project.

It looks to me like infinite javascript loop somewhere. I don't know where exactly, but I will find it and it will work later.

3 new options added starting with "Block % of..."

Try Comment on chart (low level)

I think I got the idea. What you want is to block % of Balance, so for example if you have 10000 USD and decide to block 50% of balance (or 5000 USD), to open such a lot size that will result in "Margin: 5000 Free margin: 5000". Well, not exactly 5000 for the free margin, but close to. Is that true?

And what I mean by "% of Balance" is something else - to open such a lot size that converted to money value to be equal to % of the balance. For example I have 10000 USD and I want to open 100% of that number, which is 0.1 lot because we know that 0.1 lot is 10000 in money value.

Obviously there are 2 different methods that both can be described as "% of Balance". I wonder how to differentiate them...

Now I added one more parameter to these options - MarketInfo(sumbol,MODE_TICKVALUE). The result will be divided by this parameter, but I think this only makes difference if the account is in JPY or other currency with price far away from USD,EUR,GBP.

3% is too small, there is always a limit from the broker, which is at least 0.01 lots I think. And if the requested lot size is lower than this minimum size - the minimum is taken.

Oops, I found a problem with reading the last available build, and unfortunately the problem is in the .exe, not on the server. I will create a new build now (039).

It was interesting to me when someone will ask for these blocks MT5 actually natively supports this event. I have plan to make them.

The idea behind "100% of Balance" is that the lot size increases when profits increase. For EURUSD, let's say you have 10.000 initial capital, 100% of this will be 0.1 lot (which is 10.000). So, when your profits become 15.000 the lot size will be 0.15 and so on. It's linear. There is no leverage here, and yes, with 100% of Balance it should open something that is on the lower limits side - basically the amount of money for leverage = 1.

This can be used sometimes to create infinite loop... but when - I don't know Connecting the negative output to the input has more logic. Before those little black things were bigger before, but I decided to make connections with less curviness... and now I see that their wicks are invisible in. Maybe I will try to make those self-connections to appear above the block, not behind it.

Are you trying to install the new build? Because in it, the first thing to do is to backup all the data and then to update some files because of some new rules that I've made. If you have many projects, and they have many small files, this backup process can take some seconds, maybe minute, but if you decide to close the program in the middle of the process it will hang of course.

When is that disk activity starting? Hitting .ex4 or something else?

Wow, it's named MQL4 in MQL5! I should rename it of course, but nevermind, it's the same block and it can be used in MQL5. But why are you asking, test it.

Ok, let's say you have 10000 GBP and you use 100% of Balance option. What lot size do you expect to be opened?

__Ah... we may be getting to the heart of the matter now. As you see from my screen shot, block 6 is, as far as its concerned, disconnected from itself. Could this be where the corruption is creeping in? FxDreema seems to think one thing, and the underlying code another?[/quote:cx0h0z99]
It is self-connected, notice the tiny black things around it's input and output circles. Right-click on it, hit "Detach", then connect it again with the other two blocks.

The local version of fxDreema is builted with 3rd party software and I am total noob in the world of desktop programming (C/C++), so I can't help much with the other error.