Posts made by l'andorrà

@fxdreema-1 What do you exactly mean? Can you please show an example?

@technodroid You can do it this way for buys:

You will have to replicate it for sells.

@roar Thank you for your kind words, man.

@yyaanniicckk That's not a simple question to answer. You need a variable to store the information of what happened with the last closed trade. That variable should be then be combined with your launching structure in order to identify when a new buy or sell is ready. It clearly depends on your currenty structure.

@jstap Certainly a copmplex project. At first glance I didn't see any wrong logic. However, I see all trades and pending orders are working with the same group. Maybe creating different groups for the pending orders you'd be able to filtering them better.

@jjtrader It's weird. Your logic is correct and buffers are correctly identified. Honestly I don't know why it isn't working. Have you used this same indicator in previous EAs succesfully?

@rnonnekes81 I hope you find the guy who'll help you.

@turelforex Never found that issue. Did it last for long? Is it still active?

@xyon126 Pues si existe, lo cierto es que no lo conozco, me temo. Siempre te puedes pegar la currada de hacer todos los cálculos a pelo y meterlos luego en tu panel.

@xyon126 Apparently your project is corrupt. I created it from scratch with a new project and it works correctly. Did you reuse/recycle this project from a previous one? probably that is the reason.

@joele1989 I have bad feelings about that custom indicator. It looks like a zigzag. Can you please share it?

@toto You can try this:

@ferford I already answered there.

@ferford Some issues I see:

1. Are both time filters correct? I see the latest hour on top, not below.
2. You do not need two time filters blocks if both are filtering the exact same time period. Use just one on both launching trees.
3. Both 'for each position' are specified for buys and sells at the same time. Select buys on the left only and sells on the right only. Then remove both 'is position' blocks.

@fabiobioware Why is your first block on top of this tree requiring at least 2 open trades? What if you have only one? Wouldn't it be applied?

@michele-vitulli Entonces iremos paso a paso. Lo primero a hacer es crear dos constantes en las que escribirás cada día el precio de soporte y el de resistencia:

El robot habrá que ponerlo y quitarlo cada día, de modo que los precios de ayer, ya no se aplicarán hoy y habrá que introducirlos manualmente de nuevo. ¿De acuerdo?

Ahora dime exactamente qué tipo de cruce quieres que el robot identifique. ¿Un cruce por barra o tantos cruces por barra como sucedan?

@kestra Are those conditions supposed to happen at the exact same moment the trade is closed?

@lali Are you talking about a martingale? I'm not sure. Will there be only one open trade at a time?

@yyaanniicckk I'm not a programmer but apparently that is what's happening. Try to change the names of the variable listed there (if possible) and try again.

@highmoose Can you please share the link to the latest version?