Topics created by Goatan

@goatan You're welcome.

Might be a history data problem - your terminal can't find the data for all pairs

@roar Thank you, that was exactly what i needed and has helped me understand using the variable a little more. Thank you thotheothers that helped also.

@roar said in Time as a variable:

@goatan
Working with minutes and hours is really frustrating, I have found it better to count the bars:
0_1561139465002_23546428-22a9-43cf-b62d-d3f5e946ae63-image.png

@l-andorrà said in Time as a variable:

I agree. Counting bars on the appropriate chart is much easier than catching a 'standard' time variable.

Thank you both this gives me something to look into and i have never noticed the modify variable block before.

I think this is what you are looking for:

https://fxdreema.com/forum/topic/5388/project-option-s-bug

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

These things are only visual, the EA does not care what visual limits you have for the indicator. But if you want to use these, first check this "Fixed maximum" and write 100 for it, then go to "Levels" tab and add two levels at 20 and 80. But this will not change the way Stochastic works. So the problem for the EA is somewhere else - inspect how/when trades are placed, something in the logic could be wrong.

Pass block does nothing actually, and that message has nothing to do with blocks. When EA is started it says "Starting" and when the first tick comes it is changed to "Working". In MQL4 language "Starting" shows with init() and "Working" shows with the first execution of start().

You have "on Tick" - blocks placed there are executed on every tick. Well, the ones at the top (where no blocks are connected above them). These blocks should be conditions, filters... anything that asks for certain condition before taking some actions.

Tick comes -> Check some conditions -> Do some actions.

For example, conditions might be:
No trade is running -> Check if MA5 is above MA10

and the action can be:
Buy now

Also there is a category for working with indicators. This category is named "Indicators" and it contains some blocks that are some kind of complex Condition block. Also Condition can be used to check what it has to be checked.

Indicators are different in how they communicate with the EA. They communicate with their buffers. On each of these buffers you have current value and values for each bar in the history where the indicator is drawn. A buffer is an array... if we have to say it in programming language. And "Indicators tester" is used to just see what is in a single buffer, at least to know if it's something meaningful, not crap (because there are many indicators with crap on their buffers).

Whooohooo Working again and can see the source code as well. You guys are simply the Best. 😄

I think i have got it thank you