Posts made by fxDreema

Use these two pink blocks:

For each Trade -> close

In the first block there and settings to choose how trades must be sorted, with how many of them to work, how many of them to skip and even more settings.

Maybe you want to do something like this: https://fxdreema.com/shared/jpcPqvJqb
There is a variable that is set to Bid when the upper round number is detected, but then this same variable is compared to Bid, so as a result "Round numbers detector" passes only once for a given level and after each level the price must go even more upwards to reach the next level. Plus, if you make the variable 0, the whole situation resets.

Interesting. Well, I now have brand new code for the whole website and my focus is in it, so will probably not fix that problem (also because I don't want to break something). Otherewise the problem comes from the "pips" part in "trade_sl_pips". For the "Adjust" field this keyword "pips" is special, so if you write 20pips it will convert it into something else containing toDigits... and the rest you can see. But maybe something is confused, wrong regular expression probably.

My suggestion is to change variables or to write both of them in one place.

Your newest project that I can see is called "time-problem" and there are no trading blocks in it, only time filters and Draw Line. I don't know what to say for the expiration problem.

Sometimes... but when, in what situation? Some project maybe?

All pink and purple blocks are a little bit specific, they must be used in their context. Pink blocks are to be used within a loop created by "For each..." blocks, purple blocks are to be used under "on Trade".

In any case, if you want to trail stop, you must work under "on Tick", because the stop must be always monitored. The thing is that "Trailing stop" block should not be placed right after "Sell" or "Buy" blocks, because in such way "Trailing stop" does not run on every tick.

If you want to separate trades or orders, take a look at their "Group #" parameter.

I see "For each Pending Order" over there, not "For each Trade", there is some small difference between those two blocks

Something like this: https://fxdreema.com/shared/LRRlfa6Wb
But you must be sure that you are not putting similar arrows for other reason. It's probably better to also limit orders.

Is normal Trailing stop with it's default settings work, or the problem is because of the magic number?

But they are visible And you can manually move them as well

Connect those break even blocks somewhere like this: https://fxdreema.com/demo/mt4-trailing-stop

Yes, but what is the idea here?

There are many blocks to filter time with many options inside them. Time filter, Weekday filter, Hours filter, Minutes filter...

http://prntscr.com/7scydx

What did you tried so far?

I don't know

Fixed

Some parameters are calculated from the start of the EA - dropdown and things like this. Trades count was also like this, but I moved their calculations in other part of the code

In fxDreema you need to add indicators only if you want to have them into the database and easily select them in blocks - their input parameters and buffers. Then in the code the iCustom() function is used to get values.
https://fxdreema.com/documentation/work ... indicators

Again, this indicator requires another one called "TVI": http://prntscr.com/7rxejf I don't have this indicator called "TVI".

But CustomPoint() is used all around the EA in one way or another I did some fixes in DrawSpreadInfo, sopefully it will work now.

I think it will be better if I adapt this block to work in all cases, but I don't know why it doesn't work for you. Do you really have exactly the same Time components for 2 or more neighbour candles and what Renko EA are you using?