Posts made by fxDreema

There is nothing in "Condition" that can work with only a group with trades. Here is how to do it with a loop: http://fxdreema.com/shared/ChS0MSylc
The same thing can be done with using Variables instead of Formula Results.

Now it seems that there is no input field in "Value (boolean)" that we can assign to a Constant, because there is only one drop-down True/False menu. I winder if I have to make it possible to assign Constants and Variables to those drop-down menus... but nevermind.

http://fxdreema.com/shared/NiBgwlwC
Boolean datatype is not very different than a numeric 0 and 1, where 0 is false and 1 is true. We can use Value (numeric) when we work with boolean values and there are even no warning messages in MQL4. It just works.

I don't like monuments... they are so dead!

Well, this block has parameters inside, it's also important to know what's in there and if it matches the existing trades. There is a magic number, trade type (buy, sell), market (symbol)...

Ooops, I just found that I have missed to upload the last update of "Terminate EA" that I've made weeks ago...

You can try it now.

Well, in this case why don't you put it into "scripts" subfolder?

I have an idea to make it possible to mark the project as expert or script (or indicator, in unknown future) because at the moment all the projects are considered as expert advisors, but I think if you put it into "scripts" it will work as a script.

Welllll... my point of view is that fxDreema should not create single universal EA that is supposed to do everything. That was the reason why I started it - because I wanted to NOT try to create universal EA.

You can define external parameter and add it to Condition for example, this way you can change the path after that Condition depending on what is the value of that parameter.
I just added "Value (boolean)" to Condition, you can try this for example.

But to change, for example "Stop-loss mode"... it's not impossible in theory, but I don't think it is a good idea. Actually I think I will disable external parameters for all drop-down menus in blocks. This is because they are represented as a string values, but they are nowhere documented.

Done.

Hm... I think I was confused the first time I read this question. What do you mean exactly?

I decided to just cut off the variable name if it is too long. The maximum variable name characters in MQL4 is 31.

In MT5, buy 0.1 and then buy 0.1 again - you will have a single position of 0.2 lots at the end.

First see on the buttons above where on the center you probably have one active that is called "on Tick". So, blocks under "on Tick" works on every tick! That means if "Buy now" is executed again and again and again in every tick, you will go out of money in a very short period of time.

Please, check your "Welcome to fxDreema" project and see what is the block on the top.

By the way, note that MT5 is different than MT4. In MT5 if you buy 0.1 and then sell 0.1, you will end up with no position at all, because the buy is closed by the next sell. In other words, in MT5 you can have only one position at a time.

The question is maybe if MetaTrader can do it. I don't know what programs are used because my GSM is not working 98% of the time. But if someone else has an idea...

Interesting, we have the same here: fxdreema.com/forum/viewtopic.php?f=2&t=1947
Well, the reason why I didn't added it to not make thing look too complex for newbies, and because numeric values of 0 and 1 can be used instead of boolean... most of the time. But because this is the third question for this feature I guess I must add it.

I think that Terminate EA is able to do that, after I added this part in it's code:

PostMessageA( WindowHandle(Symbol(),Period()), 0x0111, 33050, 0 ); // Self terminate EA

This method uses "user32.dll", but if dll's are not allowed, it stops the EA in soft mode - sets a variable who disables all the blocks from execution. Isn't that block working for you?

Yes, why not

I almost forgot about this, thanks for asking me again. I am in a process of optimization now, because fxDeema reached the point where it's code became too complex and too bad to continue adding new stuff. So I started to overwrite some old things. Yesterday I uploaded a weeks-long update, so now I can check what happened with those long variables

Wow, that sounds bad. Now I don't have an idea when this can happen, but if you understand how can I replicate it - write here!

Arrows seems to appear on the 5th candle. I'm using "<1000" as a condition because when there is no arrow, the buffer gives us a value of 2147483647, so the moment when the arrow appears is the moment when it's buffer value is less than 2147483647. Well, 1000 looks better than 2147483647 and that's why I'm using it.

"Signals" block is waiting for the condition (inticator<1000) to happen to pass once, and then waits for the opposite condition (indicator>1000) to happen. After the opposite condition happens, it starts to wait again for the normal condition.

dr_hassan , just to mention that I saw your project where you trying to do it, and I think you can make it, but check the link I posted above.

Today block titles are causing some problems. I will inspect that, thanks for the report.