Posts made by l'andorrà

@alphaomega It is important because I'm finding bug after bug in MQ5. Please look at my other 2 threads in this bug forum. Something serious is happenning to MQ5 in fxDReema.

@l-andorrà Am I the only one experiencing this?

No news from the administrator/fixer?

@alphaomega Don't be too harsh to me, please!

@sirboyce Impressive results. Can you please share the EA?

@sobrishariff Ok. Let me understand it correctly. You want to know when the stochastic's main line is crossing down 10. That information is supposed to be hold into a variable and then if the main line crosses up 20, the previous information is used to confirm your buy. Right?

Now two questions:

1. What happens if main line crosses down 10, then crosses up 10, then crosses down 10 again without touching the 20 level?

2. When price crosses 20 up is the crossing down information supposed to be still available or sould it be reinitialized?

@alphaomega What I don't understand is why getting the overall amount of pips (20 as you say) isn't good for you. Simply use a 'Check profit (unrealized)' block. The SL problem would be a minor nuisance the because you can the specufy it to be positioned in the lowest/highest position of all open trades.

@mohammad1373 Not exactly. You need to do what I recommended in point 2 of my previous post. Additionally you should separate blocks 7 and 15 on the left and 14 and 18 on the right. Those blocks need to be independent from the main tree. Finally, I do not recommend to use the == sign on blocks 16 and 19. It is a very restrictive contition. I would use <= for buys and >= for sells.

@marius-els Not sure I fullu understand you. Is The EA supposed to selfterminate imediately after the trade is manually open or immediately after something happens to the MA?

@suyj You can create a Constant as a multiplying number and the use the 'Formula' block like this:

@alphaomega I hate mq5 indicators.

@ramimoujaes This indcator has a problem. Each buffer has two colours and fxDreema cannot work with that. Only one per buffer should be available. I'm afraid a real programmer is required to fix it, sorry.

@guille4 Is your project maybe very big? That's not happening to me, and I guess this is because my projects are small.

@gunji80 That is happening because opening and closing conditions are happening on the same bar several times before the candle is finished. You can avoid this by using a 'Once per bar' block immediately below both 'No trade' blocks.

@billymane Easy, connect the first block with the first condition to the second block with the second condition. That way whatever youe want to happen will only happen whe BOTH block conditions are true.

@drewliedadeuce Can you please share your project to take a look at it?

@cliff-0 Are you planning to use this buttons for backtsting? I'm not sure right now but I think they are not fully operational when backtesting. Could someone confirm this, please?

@alphaomega I'm not sure, but I see you just take the newest open trade when adding volume. However you are working with several open trades at the same time. I think this is why the SL is not moved to the correct position. The EA needs to know where all open trades are to identify the final one.

@alphaomega No, I'm not using a VPS and all arrow setting are offered by default. And I didn't modify them. This is really weird.

@drewliedadeuce In general, yes. Specifying different groups to different opening trades can fix the problem. However, it will depend on your current structure. Maybe taking a look at your project would help.