Posts made by l'andorrà

@seb- I don't hink MT4 will be updated anymore. AFAIK all updating efforts are focus on MT5 only.

@sirluk You're welcome.

@seb-0 Good news for MT5 but terrible news for fxDreema. Every time a new build is released several fxDreema blocks will not be functioning correctly. This is why I focus on Mt4 only .

@vhager Firstly, that 'pass' block is unnecessary. You can remove it. Then I'm not completely sure what you exactly need. If I understand it correctly, you want a log to be printed once every two candles. Correct? If so, you will not get it the way you did it, because those blocks are on the 'on tick' tab. This means every tick both blocks will be executed no matter what. You need to add a 'once per bar' block on top for that to be checked just once every time a new bar is created. However, I guess that will no be enough because you will need additional conditions to be checked, right?

@ale Can you please share the link to the updated version?

@majinrex That depends on the whole strategy. What will that make for sure is increasing the numbers of checkings per tick.

@kk-6 I don't understand the logic behinfd that. Do you want to click on a button at any moment on the chart so that, regardless how much time is left, at the opening of a new bar a pending order is programmed? So can you click on the button ten seconds or three hours before a 4H candle is expected to be open and get the same result?

@sirluk Firstly, you can remove all those 'pass' blocks. They are not necessary. The I see you are requesting the hammer to be confirmed at the same time the trade is supposed to be open. If I understand your strategy correctly that should happen before, right? If so you need to separate that part from the current launcher.

@duepips You do not need to modify it you you want it negative. Just type -1000 in your constant. Negative double/int constants are fully functional in fxDreema.

@eren-0 Your logic is correct. Is this the whole project or just a part of it?

@eren-0 You're welcome.

@lekan4apex Do you have any initial project to begin with? If so, can you please share the link?

@ale Here you have some initial changes to do:

1. You should substitute that 'no trade' block bu another one called 'no trade/order'. Otherwise many orders will be programmed.
2. I recommen to use candle ID 1 on all operands of all blocks instead of candle ID0. That would mean you should add a 'once per bar' block on top of teh whole structure.
3. Remove one of those 'trailing pending orders and diconnect the other one from its current position to be connected below a 'pass bloc on a different block tree.

Thant should fix most of your issues.

@jukilop Sure. Can you please create a nerw thread with your questions? This thread is for betting only.

@mtrader4 But what if several crossing happen for 10 minutes for example? Which one should be the correct one, the first one or the last one?

@frank-2 All crypto payments are manually checked. That means theu need more time that automatic onex. You should wait for a few days. I nothing changed you should contact the admin.

@bjay31fx You're welcome.

@bjay31fx You should select candle close ID 1 instead of 0.

@eren-0 Did you check the pip sizes rules? That's the most common reason for an EA not to work on deriv.