And better don't touch it. I added this "cross width" option probably in december 2011, but only once I saw someone that really needed that option

I don't understand how new people still discover that desktop version 🙂

No. The desktop version uses these paths to save the output file Yes. Well, I don't know how to work with Renko in the Tester, but if you put the EA over an offline renko chart, it should work with it

I see 2 paths for "Sell now" - the first one is after block 7 and the second one is via block 16. Yes, "Sell now" will run 2 times in this configuration if the candle is new for "Once per bar".

I think I told you few times about that immediate close. I don't know what else to say 🙂 Here is that flip-flop example from which you can get some ideas: https://fxdreema.com/demo/mt4-buy-sell- ... conditions

http://prntscr.com/d0nhq3

Yes it is working, cannot thank you enough!

ndt113 -- yes that's the basic idea, might implement TP later.

Cheers

Thank you so much for your reply. Been away but now I'm back I'll try everything you've mentioned.

__

I might give this a try when I have a clear head tomorrow - what you did here definitely makes sense. Thank you very much for the idea!

-Scott[/quote:3m46rfok]

the first one is with bad connected blocks, this one is closer to reality:
https://fxdreema.com/shared/2t3NZtEIb

No. Only "Delay" block requires DLLs. I prefer to not use DLLs 🙂

Click on this History link on the right side Delete is a good idea, but if you ask me, I don't believe that Copy/Paste is a good idea. I mean, I know some users that have giant projects with 700+ blocks, and most of these blocks are copy/paste groups of blocks, which is bad practice 🙂

In few days I will upload NodeJS version of fxDreema, because I decided to use this platform and I rewrote the whole thing + I changed the database as well. The forum will be NodeBB, which is the only forum I can find for NodeJS 🙂 New features... I don't know, even now people don't understand everything. Maybe it's better to make everything easier to work. Also, I think I have to write descriptions for most options in the blocks. I will also probably do some MQL4/5 code optimizator, because the generated output code needs to be cleared from unnecessary stuff.

http://prntscr.com/cyfdic

I guess I have to make filter block such as "Pending order triggered" or add some option in "Trade created". But if you are using "Trade created", it should not pass if pending order is created. I just tested it and it works as I expected 😮

Thank you very much for your wonderful help. I will try it and see 😄

__So this can be used to stop EA from trading for a certain period?[/quote:390w9c1t]

yes, with few conditions you can do this

This is job for some indicator 🙂

To be honest, I don't understand Excel very well. I don't even know how to open this .csv file with it. But I'm sure that Excel has many different ways to format the data, so I guess this is what is going on

I'm aware about this problem in the desktop version, but I stopped making desktop versions year ago. Since then I rewrote everything from PHP to NodeJS and I will update everything on the server probably after few days. In other words, PHP is history, as well as the current desktop version. I of course tried to find why this problem appears back then, without success. I used ExeOutput for PHP to make it, and this software is not only buggy, but also unsupported.

Thank you very much for your reply

__oh yes the answer why I first set a TP and then I delete this. In my trading-idea I am looking for hammer in DAX. Sometimes a hammer starts a big move, and I only get a little part of this move. So first I set a TP, and when the PAR SAR works, I set the trailing stop on the PAR SAR and delete the TP.[/quote:17v83jqy]

ok so you need working in onTick section, here you can try delete TP when you set to 0.

You can make a shared copy as well. I hope you are not asking me how to send e-mails with attached files 🙂

If you do the whole process forward, I mean you detect condition 1 and then Condition 2, then meanwhile you can just increment some Variable while the EA is working. Counting candles is for the case when you somehow detect the previous candle NOW. If this is the case and you somehow know the ID, there is no reason to search for the time of the candle, because you already know its ID. If the ID is 15, then there are 14 candles between candle 0 and candle 15. But with the EA it's kinda tricky to find the ID of a past condition, because the Condition block works in the current time and does not search for past conditions.