Posts made by fxDreema

I'm showing yo how to set value to a variable (one of many ways). As you can see, I'm doing this with the minimum blocks possible, just two of them. It's up to you to set your variable on the right time in your project.

1 - Yes
2 - Magic numbers should match. Well, in the EAs generated with fxDreema you don't control magic numbers directly, but this is done with the input parameter called "MagicStart" and Group numbers in blocks. The short answer is - for those 3 EAs use the same MagicStart and don't change Group # in blocks.

Look at the top 2 parameters in Draw Line. I know that they are confusing and you probably don't know what they are doing (me too ), but they cover 4 different situations. To always redraw the line when this block is executed using the same name, set those like this:

The block can... : No
Redraw the....... : Yes
Object name..... : BBB

And you probably don't need "Delete objects" in this situation

I don't have this indicator, but normally it works: https://fxdreema.com/shared/aPNDHmmle

In exacly the same way, but select the indicator instead of Candle Close

Look at block 3 here: https://fxdreema.com/shared/efAI5bkbe

Or here: https://fxdreema.com/demo/mt4-variables

Показвах на някой ей това: https://fxdreema.com/shared/efAI5bkbe Гледай 3 блок, там се слага стойност в променливата. Може отгоре да имаш Hours Filter -> Once a day, като часовия филтър е настроен от 6 до... еди си колко часа. Идеята е да се сложи стойност в променливата в първия удобен момент след 6 часа. Ако просто имаш идея и искаш да я пробваш на тестера, давай така, това е най-бързия метод щото няма да ти прави калкулации постоянно по време на теста.

За другия начин трябва да видя нещо в Condition -> Candle. Там сега има опция за Candle ID, но трябва да направя опция за време. С времето обаче е малко по извратено, трябват и калкулации за да се изчисли ID-то на точната свещ спрямо настоящето време.

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

In every input field you can put pure MQL4 code, and sometimes this is even easier, like the way I used those OrderProfit() functions. Of course, you should understand what OrderProfit() means, but I think this is easy.

I found a general problem before, but in fact it's not clear for me what are you trying to do with these variables?

Something like this maybe: https://fxdreema.com/shared/kv5ZcQmVb

https://fxdreema.com/shared/YyJYV5LPc

http://docs.mql4.com/trading/orderprofit
http://docs.mql4.com/trading/ordercommission
http://docs.mql4.com/trading/orderswap

It depends. Now I'm thinking for a block similar to "For each Trade", but to load a group of trades, so then different values of that group (min, avg and max of something) can be found somewhere in "Condition". But people have problems working with "For each Trade", so I don't know what will be the best way to do something like this

In "Modify Variables" use the "(on trade)..." category, not "(in loop)..."

"(in loop)..." is used when you are using block like "For each..." to load trades
"(on trade)..." is used when you are under "on Trade". By the way, you can still use "For each..." block and "(in loop)..." parameters here

Yes, for blocks like these that contain internal counters it's very important where they are connected. Their current state depends mostly on the number of times they are executed. You know that under "on Tick" the block on the top of the group (of blocks) is executed on every tick, often multiple times per second. Don't forget that

Expert Advisors are not just scripts, they are programs based on events. When you have events, then you have states. This requires good imagination

These blocks are like black boxes There was a time when I decided to make it possible to output some values, but then I stopped developing this option. But you can always do simple calculations using some pink blocks and Variables.

Exactly 100 pips - not at all. When working with prices, never use "==", this is an important rule. You can look in the code of this block, it uses ">=". I think this is what you want, but you can also get the level take-profit in Condition -> (in loop)....

Don't forget to use "For each..." when you are working with pink blocks

Trailing stop (each trade) -> Trailing stop is... -> Custom (level)

Here is what I found, you can assign hotkey for each script: http://forum.mql4.com/32370

Can you try on your system how it works now. Here is my test EA https://fxdreema.com/shared/aEnXaRG3e It should open a new position and then close it immediately.