Posts made by fxDreema

Yes, 1000 is the the maximum value for most brokers, but you probably need to have millions to be able to open such lots, but this will probably never happen

I uploaded this, also with other visual updates.

So, the keyword is "Bucket". You will find this group now called "Bucket of Trades &..." and I marked it as experimental, which means that I can decide to make some changes. Very often I get better idead right after upload something

There are 3 blocks inside. Each one selects a group of trades and there are very basic filters. Then in "Condition" you can find a new category with the keyword "Bucket" again. This is where you can choose what value you want to get from the selected group. Count, Profit, SL, TP, Lotsize... such things are now available and you can also choose to get the Total, Average, Maximum or Minimum value.

Additionally there is some advanced option that I just decided to use. The idea here is that you can write some condition in pure MQL4, something like:
OrderType() == OP_SELL
which will filter only sells for the actual calculations. So, the bucket can have Buys, but with this option they can be filtered. I'm not sure if it's better to keep this option over there or directly into the Bucket-blocks, but that's why this is still experimental, I will decide.

Also, multiple different buckets can be selected at any given time. Each of them is identified by color (which is Bucket ID). By default in "Condition" you will work with the bucket that was selected last, but if you want you can select 2 buckets (before "Condition") and compare values from both of them in "Condition" by using those colors (Bucket ID).

I can in fact add blocks like "close", "modify stops" and everything similar to the pink blocks, but for now I don't know what new can this bring to the builder.

I'm still fixing some issues with the generator of blocks, if we are talking for the online version. But I think that you don't need this at all.

There is an option at the bottom of all Buy/Sell blocks for the comment. Whatever you write there, this will be the comment. Then you can't modify this attribute anymore, only the broker can

Do you really have this situation? Because if the maximum is really 100 lots, I think that there are also other limits that will most probably prevent you to open even those 100 lots.

Such thing was never requested. But here is a way: https://fxdreema.com/shared/xjBTMFbkc

I have a variable with initial value of true. Also, it is set to true every time. Then I check the last 10 closed trades. If one of them is Buy, my variable is set to false, which means that not all trades are sell (there is a buy).
The "break" block is to stop the loop when there is no need to do more checks.

What is the practical use of this?

Can you send me some .mq4 or .mq5 file that cannot be imported? Because I did few fixes in the past and now I have no idea what else could be wrong.

Well, under "on Tick" any blocks are doing what they do in the current moment. Conditions are checking things now. Of course, old data can be used, but it is used at the moment. If you know at which candle the crossover must happen, then you can detect it for this candle. Otherwise, of the crossover can be anywhere... well... why not just using > or <, because if line A crosses over line B at some moment or candle, then after this cross line A is > line B for sure.

When a block runs and does what it has to do, it's output becomes active, which immediately causes the next block to run. This will continue until some block of the chain does not pass or the chain ends. Then other groups of blocks come.

Try this value instead 0.1:
0.02*AccountBalance() / MarketInfo(Symbol(),MODE_MARGINREQUIRED)

Or this:
(2.0/100)*AccountBalance() / MarketInfo(Symbol(),MODE_MARGINREQUIRED)
... but it's important here to have one of both values - 2 or 100 - written in this way - 2.0 or 100.0. Otherwise 2/100 returns 0 for some stupid reason

I fixed this in your project and I should fix it in the generator, but for now I will just suggest to not use those checkboxes for optimisation too much. Better use Variables

I don't know for copyright problems, but you should be able to import .mq4/.mq5 files from the desktop version. The opposite will not work now, because the online version is newer now and have some different things and I'm not sure for the future of the desktop version for multiple reasons.

No, manual trades are always 0. The magic number (and the group, which is basically the magic number) exists only because of expert advisors. Maybe if you set the MagicStart parameter to 0, so the EA would normally works with manual trades, and then you can use Group # as a real Magic number.

Magic Number (the real magic number that the trade has) = MagicStart (which is an input parameter of the ea) + Group number (found in blocks)

http://prntscr.com/8bywrk

When blocks are not chained, then their numbers can be important. Blocks with lower numbers run first. But you should be able to see how things work in backtest.

I already have it, but when I do something new, I'm normally trying different ways, because in the process I can dedide that something needs to be added ot removed

I understand, but the other MM options are located in the same select menu where Martingale is

No "If trade is running" is needed for Trailing stop by the way.
Maybe something like this: http://prntscr.com/8bis31

Now only possible with variables, but I'm currently working for new category of blocks to do exactly that

То и аз съм го изгубил и трябва да го намеря. Има логика в т.1. Още преди когато го правих и лично си поиграх с различни стратегии и начини на отваряне на поръчките, но винаги беше подобно на Мартингейл - работи, работи, работи... до един момент в който нещата се изпускат и положението става прогресивно зле. Не съм пробвал какво ще стане ако се обръша внимание на най-старата поръчка. Малко ме съмнява да стане чудо обаче, и това да ти кажа си е и една от причините да несъм го направил официално блокче, щото най-много да започнат да ме разпитват и за него, а то да няма сериозен потенциал. А пък ако има сериозен потенциал, тогава защо ще го показвам

Някои неща може и да са разочароващи, ако са умишлени ограничения които съм сложил. Но и аз се развивам в правенето на код, разцъквам програмни езици и пробвам различни неща, съответно прихващам някои полезни практики и най-много да реша да ги вкарам в генератора. Полезните практики обаче често изискват някакъв първоначален труд, а после се отплащат. Примерно това като ползваш променлива да й сложиш читаво име. Заради това разкарах тия ResultX променливи дето се създаваха от Formula и сега всеки трябва да си ги пише ръчно ако иска да ползва Formula

Иначе да, появиха се доста бъгове, ама ги поразкарах. В крайна сметка системата сега е по-бърза и най-вече по-стабилна. Много от бъговете бяха разни дреболии дето съм сбъркал в кода или неща дето съм забравил да направя. Докато преди положението беше такова, че ако пипнех нещо някъде и сайта се чупеше на няколко други места и беше безбъгав просто защото не смеех да пипна нищо в него

В момента подготвям нов начин на работа със списъка от блокове с акордеон ефект. Малко е шарено, ама ей на да видиш: http://prntscr.com/8bhyw0