Best posts made by roar

@xavier-joao-mpete not for free, hehe. We can discuss in PM.

So you want a fixed Y point but moving X coordinate? Or both fixed - then you could use "rectangle label" object.

There is a function called PipValue hidden in the background, you can test what it gives.

I think what's needed is x value as a datetime, y value as a pixel coordinate. A mix between label-type object and normal object.

So one option is to use rectangle label (fixed pixel coordinates) and continually update the x value with ChartTimePriceToXY function (ignore the Price->Y conversion in that function).

@fideld003 I see youre a fast learner - this isnt the most simple example lol

1. Yes, its usually best to set variables zero at the beginning, you will modify them later anway - thats why they are called variables

2. The color fields are a quick way to set new values for the variables. White, orange and yellow fields correspond to the half circles around the blocks: white is something that happens before the block, orange and yellow are outputs depending on block type. In case of a loop ("for each..."), orange is something that happens on each loop iteration, and yellow is the "exit door". So, to count buys:

• reset buys variable to 0 before beginning the loop, to erase any earlier calculations
• for each buy trade found with the loop block, increase buys by 1
• when loop is complete, take exit from yellow output and move to next part of the project

3. The custom code has a logarithm calculation. Logarithms basically scale big numbers to smaller numbers. If youre using chrome, you can try "ln(20)" in the adress bar - it gives 2.99.
   So, if there is 20 buys open, the lot value for next sell order will be
   0.01* 2.99 * 2 = 0.0598 = 0.06 (just as in your picture)

The 2nd line is just a lower limit for the lot amount. MathMax function picks the bigger value in the parenthesis. So, the line reads as "set lotA as itself or 0.01, whichever is bigger".

@LightMasterSunrise youre in way over my head too, lol

If you have the mql5 code, I can surely help getting it to fxdreema format

@Archer here's some example
https://fxdreema.com/shared/h6BiNKJoc

@Archer pip values on JPY pairs can be messed up.
Try replacing the Pips with a _Point conversion

@Archer if the EA seems to not follow the 2 pip rule, dont add more rules but instead troubleshoot why the 1st rule is not followed. This can be done by simply printing out the values the EA looks at:
https://fxdreema.com/shared/1ihsjoy2d

The problem with tight range breakouts, those "sqeezed springs", is that usually the "tightness" is only because quiet trading on a holiday, or early Asian session, basically when most traders are sleeping. It is usually not anticipation of big jump. So you need some kind of indicator that takes the expected volatility into account as well.

Forex can be traded 24/7, but there are undoubtedly quieter periods during the 24-hour day. Just put ATR to a chart and see how predictably the average volatility makes it cycles. Like a sine wave.

@El_Moein seems like it. Next step I would crete a fresh project and try again with the fxdreema block.

What does this output for you?

test.ex4
test.mq4

@littleleg here's a working example of a button, hope it helps
https://fxdreema.com/shared/4LWM6r3Ac

@mee-air the button is created in the On Init tab

https://fxdreema.com/shared/0pXpK1Cre

@cmuphyfx it seems to happen on a fresh project with only one condition with TEMA. So it is clearly some typo in the MDLIC_indicators_iTEMA class.

I cannot fix the source code of fxdreema itself (unfortunately lol), so there's little I can do here. Maybe just get a custom indicator that works the same way as the default TEMA in fxdreema.

You could use some arrays and loops, but I think the more "robust" solution is just to get a custom indicator that has the MA built-in.