Posts made by fxDreema

The thing is that if we select a group of trade in a single block, this will be just another term "group" in the builder. So I decided to color-code those groups. Instead of input field where you can write 1, 2, 3 or whatever, imagine that there is drop-down input with few options for color - red, green, blue, yellow... So in one block you select group of trades and certain color is associated with this group, then in "Condition" you can select that color and work with that group of trades. Does this sound good or it's better to use numeric or string values for this?

Another issue is, people don't really get the idea of such blocks that are loading something trade in the memory (like "For each Trade"). I was thinking to not making new block for this, but doing all the selection of trades in "Condition" directly. The problem with this is that 1) you need to manually edit all settings for each operand in each Condition block and 2) selecting group of blocks over and over again is not the best idea.

Well, it's very similar when using indicators. If I want to use the same indicator in multiple Condition blocks, I will select it over and over again in the blocks, then MetaTrader knows how to reuse it.

If you have some ideas, what will be the best way to do this...

Ох аз на това и после му правих промени, размятах го напред назад и сега не съм сигурен коя и къде точно му е последната версия. Иначе имах идея и да го пусна официално, не помня обаче защо се отказах. То работи ли по принцип, дали се експортва с него, и виждаш ли го в https://fxdreema.com/studio?

Иначе да ти кажа сега точно не ми е приоритет това блокче, че има и други работи за оправяне. А и мисля че в един случай такъв блок може да се окаже ненужен. Нали има една опция за събиране на поръчки в една, "Multiple close by" мисля че се казваше. Това нещо не се поддържа изцяло като код, но май с известни условия може да се получи. С това играл ли си си? Комбинира насрещни поръчки в една с общ лот, и май го правеше със спестяване на някакъв спред.

This will not work if stops are calculated in the moment of placing the "pending order", which will be a horizontal line or something similar. But if you think that "Buy now" and "Sell now" canbe used in the future, then it will work and I can also make some example for /examples. Is this the case?

They will be available

But I did exactly that and I wrote about it few posts above. Here is the picture again: http://prntscr.com/869vpe It's not a button, but is still works.

When I export this, I can reimport it without problems. Can you send me .mq4 file, so I can look what's in it? I am probably missing something small, but there is no problem for me at all and I don't know what is it.

Today I was working on some javascript functions, but tomorrow I will fix this scroll problem

As this is a little bit complex, it's not my priority now. But it can be made, I think, using existing blocks. The idea is to create for example horizontal line, and then to check when that line is crossed. When that happens => create a new trade.

Well, I am always doing something, I didn't said that I will start doing exactly this right now. And you know... even if I do something new, it's probably not the best idea to use it right away.

More memory... this is not a microcontroller with 64k of memory. Even if you define 1000 more variables, there will be no difference for today's memory sizes. And each generated EA contains many more functions and variables compared to some that is manually programmed.

You need to see this example by the way: https://fxdreema.com/demo/mt4-wrong-closing-rule

I think that optimization checks for drop-down menus does not work, but I will not recommend to export those anyway. The problem is that you probably don't know what the possible values of such an input are.

For the variables thing, I will do that later, because this requires some additional checks. The issue here is that we can use Constant or Variable in different ways, not only by right-click and select.

Areas. I was thinking about this before, but the problem here is what happens when you collapse or expand an area, because there can be other blocks around - what happens with them? Especially when you expand.
I think I prefer to make something like pagination, to be able to put some blocks in page 1, other blocks in page 2 and so on.

Interesting, I fixed some problem with importing like 2 days ago, now what can be wrong again. Send me some project that fails?

I noticed that if the properties window is higher than the available window, then when I try to move it, it jumps somewhere. Is this what you are talking about?

Eventually I will remove those block numbers. But I can't get the idea to highlight blocks in a different way (from the way I did it now). There are few working fields (on Init, on Tick...) and for each of them the space available for putting blocks is unlimited. So how to see all blocks at the same time. Only if there is some shortcut created, I guess, but this is not highlighting of the blocks themselves

This easy way is on the way. It will probably be a block that will select group of trades and then in Condition (or any other) it will calculate different values using those selected trades.

But in fact this can be made pretty much easily using Variables and the result will be better. In "For each Trade", in it's second panel "Variables", if you have variable that is V1 there, write this in it's input (the orange color): V1+OrderLots(). Then use the yellow output of this "For each Trade" to connect something else.

Ok, but what is "not work" now mean?

Which one of your projects can I look at to check this?

__well signal will be taken once the current candle close so multiple fresh cross is not the isue...[/quote:28y6txsm]
When you work under "on Tick", blocks will run on every tick. "Condition" block is a simple "IF", it compares two values and goes to one of it's outputs. In case of crossover, there are two IF, but again, it goes to one of it's outputs while the crossover is true. And the crossover can be true for the whole candle, which is multiple pips.

Then what do you want to happen?

http://docs.mql4.com/runtime/testing

Timer and ChartEvent events are not handled in the Strategy Tester.

Because you can't use the compiler with MetaEditor itself, I think that the problem is between Windows 10 and the compiler.

I was using Windows 10 (preview build) the last year when these problems started. All my programs worked well, only MetaTrader was having problems. I wrote about this in their forums long time ago, see:
http://forum.mql4.com/65673
http://forum.mql4.com/65633/page2
(I am JDeel)

Then I installed 8.1 and now I don't even want to try Windows 10.

You can see the latest reports for Windows 10 in their forum: http://www.mql4.com/search#!keyword=windows%2010