Topics created by varso

@varso Congratulations.

You're right. Same happens to me. Is there any real programmer here, please?

it works. Thank you very much
What i did is that i wrotte manual .
i find input in code of mq4
0_1585080166414_2020-03-24 21_00_46-MetaEditor - [adaptive-relative-strength-index-smoothed.mq4].jpg

and wrotte it in fxdreema
0_1585080196175_2020-03-24 21_01_30-neco - Opera.jpg
you see the problems were some nonspecifict input.

Thank you again for help

There is some JavaScript error that happens when the file is being read, but I need to find it and fix it. I don't know how long it will take, so if I don't fix this soon, you can just add the indicator's data manually.

It has 2 buffers and these are obviously the inlut parameters:

int TrendCCI_Period 14
bool Automatic_Timeframe_setting false
int M1_CCI_Period 14
int M5_CCI_Period 14
int M15_CCI_Period 14
int M30_CCI_Period 14
int H1_CCI_Period 14
int H4_CCI_Period 14
int D1_CCI_Period 14
int W1_CCI_Period 14
int MN_CCI_Period 14

Fixed 🙂

It works now. Thank you very much.

Yes, this is very ugly. I can feel the problem, because I also have it when I'm programming something. I have seen such pictures many times before and for sure I need to do something about it, but you can also follow some good programming practices.

It's important to separate things. I can see you have some groups of blocks separated from other groups and that's fine until you make connections between them. And obviously, when there are too many connections you can't even see what is connected to what anymore. So try to isolate each group of blocks and don't connect one group with another... at least not with so many lines. There is also a block "Run blocks". Also, note that blocks numbers can be also words and if you use "Run blocks" I will suggest to work with blocks who have words instead of numbers.

It's important to also combine things. If you have 2 or more groups of blocks that contain the same blocks, try to combine them. The idea is to have only one group of blocks, but to run it multiple times. Something like functions in programming. Well, functions have input arguments, while blocks don't. But Variables can be used in blocks, which is something similar to the arguments.

Don't put everything in the visible area. By the way, you can also put some Areas here and there and separate groups of blocks that way.

Thank you.
it works

Oh my god
Thank you. It was my faul i wrotte it wrong. Now is correct. 😄

https://fxdreema.com/shared/IGWcDxu1c

And what do you want to do? The indicator's value can be stored in a Variable and then converted to 0, but why?

But why don't you create those trades directly in this chart 😮

Now i have idea. its simple. run the second condition only if bid price was under first low. 😆

Yes, at the end the magic number must be the same, it is always specified. Even for manual trades and orders it is some value - 0. Look here: http://fxdreema.com/documentation/proje ... d%20groups
Normally EAs work on every tick, this is "on Tick" in fxDreema. "on Trade" is not native for MQL4, I added some functions to create this trick. Use what will do the work.

Ok i make it this
http://fxdreema.com/shared/weYx1sOKc

Now start when new day will come

__Work with Candle ID > 0. Click on this "More settings" text to see this option. It looks that for the current candle there is no information that can be used, but for already finished candles there is. I think more custom indicators should be like this :)[/quote:1cykrli6]

Thank you.
You have right. The indicator looks one candle backward. I must watchs one figure on this in future.

If I'm not missing something, I think this will work:

Condition - Once a day - Start trades loop - (in loop) Modify

This is modifying stops once a day when some condition occurs.

__I'm not sure that I understand, but I can discuss the example.

First, you detect when a trade is closed, note that this will cause the next block to be executed once.

Then you have a loop, which normally loads all trades one after another and does the next things for each one of them. I guess you have to put value "1" for Not more than N trades parameter.

Then you have "Pips away" block, and in this case there is no way for this block to react, because if it is executed once when the trade is created, it still has no profit. An no, this block does not work by itself somewhere in parallel universe, but it does what it is supposed to do when it is executed (and this is true for all blocks).

The last block - well, if the project is like it is now, it can probably close part of the volume for another trade that is running (not the one that is created). That's because now the loop (block 3) works for all trades created by this EA.

If you want to close part of the volume when certain profit is reached, use that loop under "on Tick", and place "(in loop) Once per trade/order" before block 5 to not execute it more than once for a trade.[/quote:3ns3jrur]
thank you its help

__Look from NOW to the PAST. This chart you can see - this is all past data which is available for calculations. The same with indicators. Everything you can see on the chart is represented as numeric values in MetaTrader and they are available in every moment.

EA works on every tick - when a new tick comes, you check something and do something if needed.

Check condition(s) Do action(s)

To get the value of the Nth candle from the past, there is a Candle ID parameter. If it is 10, this means that you work with the 10th candle from now to the past. That means you can check NOW what was happened in the PAST. There is no need to remember if some condition happens NOW and check that in the future, because this event (and many others) will be in the database.

In short. When working with conditions in some EA, the way to deal with them is from now to the past - when a tick comes, you can have a condition that can check something that happened in the past only by setting Candle ID parameter (aka Shift parameter in MQL).[/quote:21vwz6dd]
oh my good
Thank so much