Posts made by miro1360

you can change the code like this:

which will run that function only once, when both ticket numbers are recorded

... or you can create another rearrangement of blocks too, like this one:

where the custom code block happens after all the cycles are finished
but in this case, custom code block must have its ID number larger (yellow circle) than any number from the green circle

... each for loop can go through all the trades (can happens more than 1x) and condition blocks as filters can be added (and record only that trade, which will match the filter) ... but thats your job

The function PositionCloseBy is from the Trade.mqh library and belongs under CTrade class and therefore an object must be created.

https://fxdreema.com/shared/E5T9pyT8e

from FxDreema generate only mql5 code
open generated code in the MetaEditor, in your computer

add this include in the top of code:

Above the OnInit() function add this CTrade object Trade definition:

Click on the Compile button in the MetaEditor, it generates ex5 file and done

I suggest you to read all the comments too, they may contain an interesting reply:

https://fxdreema.com/forum/post/20720

generate data in excel, save as .csv
import these data into metatrader (Tools - History center - Import)
consider some dependencies (close[1] == open[0])

it is not my indicator ... so what can I say about ....
buffers there are in the separate window as lines
arrows are not in buffers, so you can not select arrows from buffers in this case

perhaps you can check the arrow with condition blocks, its color, date, but it can be quite tedious ......... or rewrite the indicators code to use arrows in buffers

you can easily avoid onTimer function,
this is without onTimer (not tested )

0_1547316058979_miro1360_GravityBE_1.0_noTimer.mq4

edit: seems be not working in tester

It was long ago ... Do not import it into My Indicators. Place it on the chart as indicator together with EA, it should plot the line automatically and you can read the line with EA (I do not remember its name but you can find it by listing chart objects).

these enum parameters (drop down list) have unknown number, that means .. you can find them manually, run EA in tester up to the end and indicator appears (first one with parameters as EA has), next place the same indicator into finished chart (with similiar parameters) and you can see, that it is not the same, that means you must find/match the right ID of parameter (in the EA start with 0 and try to match them :D) ....

maybe it can be, all parameters and buffers must be added manually

for simplification use a cross of 2 moving averages, you can get similiar results

try this:
https://fxdreema.com/shared/rW0qyPdQb

this example returns 0 ... but you can edit it in many ways, ... lets say user enters wrong value, the previous value can be returned, and so on ...

Ahh this one ... yes it seems be dead I am sure that admin repairs it

https://ctrlv.cz/shots/2019/01/10/m3Kl.png
on my side it is working, I tried chrome only ...

Simplify this whole mess into more parts, like A,B,C,D,E and than try to combine them together, each one needs intensive testing with a lot of visual checks (like comments are). Each part should be defined in logic and math steps. To find these math+logic steps is the basic language to talk with fxdreema flawless

When you find these logic and math steps, than you can start ask, how to communicate with these two CFDs correctly. One is faster than other, so you have more possibilities, like:
A) create 3 EAs, first one for collecting ticks from Nasdaq, second for SP500 and third EA working in onTimer section, the main communication between them can be with Terminal variables

B) or you can create one EA for all symbols only in onTimer section, with faster period

C) or one EA where blocks are in onTick section and this EA is placed in the faster symbol (Nasdaq)

This is not about skills, but it is more about time. You have to invest a lot of time for something where the percentage of success is minimal. Well success, I also mean little success

Separate comment block form other blocks, place it alone, like this:
https://ctrlv.cz/shots/2019/01/03/U4W1.png

or "re-run" this comment block with the block called Run blocks after the update of each variable

How is the comment block updated?

I think, you do not need arrays for that ...

https://fxdreema.com/shared/UkGDvOKud

what exactly do you need?