Controversial posts made by l'andorrà

@truongvnd Can you please share the link to the project instead? That would help more than the screenshot.

@steven888 You can contact the admin here:

https://fxdreema.com/contact

I found a new challeng for miro ;). In order to complete his outstanding tutorial on custom indicators I would like to suggest how to deal with a common problem for MT5 users like me. How can mq5 indicators be recognized by fxDreema? Let's see this example: the humble accellerator oscillator. This is its mq5 variant when we drag it into the chart:

Apparently easy. No parameters and just two buffers, green and red. However, this is what we see when we try to upload it to our custom indicator's pool:

As we can see, both colour buffers are embedded into a single buffer 0. That means we cannot choose different colours for buy/sell conditions because both are offered on the same output buffer. How can we deal with cases like this?

BTW, this is the indicator for MT5. 0_1564065320571_accelerator.mq5

@Hoangmai Ok. Can you please share the link to your project instead of uploading a picture? That would help.

Could you please share you project to take a look at it?

¿Me confirmas la respuesta a la primera pregunta, porfa?

@behold In programming there are ALWAYS better ideas. All codes can be optimized. However, I'm not a programmed, just a fxDreema user :(. I can just recommend you what you said. Try to isolate segments of your project and test the separatedly. It will take time, but you will find the issue sooner than later. However, please try deviate as many blocks as possible to the 'on trade' tab. That will remove processing requirements to execute all those blocks on the 'on tick' tab.

@behold Wow! 367 blocks on the 'on tick' tab. That's a lot of processing requirements for your MT4. Did you consider the possibility that part of the issue is that too much time is required to process all that code every single tick?

Use a 'indicator is visible' block instead. That should work.

Is it the same indicator used in this thread?

You current configuration of the 'for each object' block is searching for one object only, not many. You should remove that limitation. Then the correct order will depend on how many objects that are NOT arrows are also present on the chart. That makes the A-Z or Z-A order to search for them too when you don't need them, necessarily.

@vish You can do it this way:

I guess it can be made via custom code. I'm interested in that too. I hope someone can help.

You should select the lines via an orange 'for each object' block as a loop instead.

@Jaico Me temo que no. Cuando más indgo más veo que el problema está en los bucles usados en fxDreema. Son una auténtica pesadilla para el optimizador. Pero gracias por tu sugerencia.

@coinmaster Initially I would agree with what Tipsy says. Most of custom indicators are repainting and this is the reason why they don't work in fxDreema. If you paid for it, I understand you don't want to share it, but if you want some serious help to fix the issue we need at least a link to the EA. Do not share the indi if you do not want, but we can only guess what happens in the project if you don't share the project.

What do you exactly mean?

@ramimoujaes Then you will need 4 variables. Two for yesterday's high and low and the other two for today's high and low:

And then we can filter that price today is within yesterday's high and low by comparing them to today's high and low:

@xyon126 Exactly. You need to insert those variables in your different buttons to get each number.

@Hellzer I don't see the logic behind that. What's the point of changing the TF in the middle of the backtest?