Posts made by fxDreema

https://fxdreema.com/shared/je4AAy48

Maybe there is some indicator to do that?

Try Condition -> Market Properties -> Ask, Bid.... and change Tick ID

Yes, because you are using two blocks now This option is supposed to create 2 orders from 1 block. If the block is Buy pending order, it will add second Sell order.

mcmillan, I just added this OCO option, find it in Buy pending order and Sell pending order. I use the comment attribute of the second order to store the ticket number of the first one, so they are linked by this comment. Then, on every tick the EA will look if one of both orders is missing and will delete the other one if that is true. The overall backtest speed is probably now a little bit down again, but this happens when I add options Notify me if something is wrong.

peteyteichroeb, I will suggest to use normal strategies with SL instead of these hedge strategies. I sent you some examples and good luck with understanding them. I also have big troubles creating such strategies, but most importantly, I think that this is not needed at all, because hedging (in the same symbol!) is nothing more that some very weird way to make things complex and hard to maintain.

No, it's built-in Chrome in the local version, there is no other type of browser there. I was talking about the web version

No nooo.... under "on Trade" you should filter the event. This event is fired often. And look what you have - If trade/order exists -> Delete pending orders. The same as if you only have the command of "Delete pending orders"

I never traded like that and this idea was never close to me, so I will ask something stupid here. If OCO means to have Buy and Sell order at the same distance from the current price, is it also right to say that we can have OCO with two Buy or two Sell orders (stop and limit)? I mean, is there some practice, someone is doing it that way?

I tried to give another number in some block... no problems: http://prntscr.com/73uuq3

What can I suggest... another browser? I made it in Firefox, but also Chrome should be fine. It's Chrome in the local version by the way. IE, better don't use it
Also, you can try this: http://prntscr.com/73uv65

How do you feel with such a big project? I think that fxDreema is not very suitable for big projects, it easily become a mess, but no one complained about that

Manually opened have magic number, which is 0. What is magic number... look here (I know it needs to be updated) https://fxdreema.com/documentation/work ... d%20groups

Yes, in blocks that have the Group number as a filter, you can use values like 1,2,3... multiple group numbers separated with comma

If it works, yes. But I think I'm gonna add some option for this OCO thing, because there is always someone asking for this.

For the Highest and Lowest price, look at the candles on the chart where the EA is working and find the Highest/Lowest price for the given period. The value that the EA calculates must be the same with the value on the chart where the EA is set to work. Not with the value in different symbol in different timeframe in different broker and as what I can see, different time offset.

http://prntscr.com/73gfo0
http://img.prntscr.com/img?url=http://i.imgur.com/iMRE48g.png

This shows Highest and Lowest price level between 00:00 and 12:00 for the current day. If the time if somewhere in between, it shows Highest and Lowest between 00:00 and that time. I want to know what is wrong here:

https://fxdreema.com/shared/ujhC1tQgd
http://prntscr.com/73g96u

You have 20 blocks to create orders! This is like a boring game for me now, I only know that I need to find in which chest the treasure is. But my mind prefers to think about something else.

What about some simple EA made out of 4-5 blocks that will show me the problem right after I add it to the chart?

Value -> Numeric

Write something in those empty title fields! If they are empty, the data will be skipped as well!

Then, to use those (in loop) values, a block called "For each Trade" needs to be placed above. Maybe it will work like this as well, but it's best to use it. The time will probably appear with it's integer value.

In the block called "Condition", I guess...

For the time filter, the problem is that the backtester runs the EA on every tick, where every tick is generated. Often there are few seconds difference between two ticks. So in the tester you just can't do something on every single second. And this is also pretty much true for live trading as well!
You can be sure that the EA will so something between 12:00:00 and 12:00:01 only if the EA works as a clock, which is only possible with it's Timer event. But again, the Tester does not have such Timer event, it only works with it's generated ticks that appear in irregular time periods.

I don't know what is the idea of this EA. Yes, I checked the blocks structure and I tested the EA, but I don't know it's strategy. And as I saw, it actually have 2 different strategies that can be changed with some button. If you give me some small test project where I can see exactly what I need to see... fine. Or you can give me screenshots of what is wrong. But if I have to explore everything in this EA...

I did some visual changes here: https://fxdreema.com/shared/dceHpggEd

Something as big as this must be put in visual order. Which is not always an easy task. This is where I lose most of the time in the project called fxDreema, I always make some visual changes in the code

Those blocks Turn ON, Turn Off. It's enough to turn off one block and all the blocks connected after it will not have the chance to run anyway. And it's probably better to give those blocks (to be turned on and off) some good name. Yes, block IDs can be text, not only numbers. But I'm not sure that using these blocks is actually a good idea.

I notice that you like to connect blocks in parallel. This is not always a good idea, because depending on block numbers you can get different results. Look at the very bottom blocks in my version of the project - I connected them one after another and I think this is the better way, it's more clear.

Those Formula blocks... here it's best to calculate vales right before using them. You have a group of Formula blocks in the middle of nowhere... who knows what is going on with these values. It's also a good idea to give good names to their Results. It's not mandatory for the results to be like "Result202", you can give those any valid variable name like "AllowedToSell". Also, you can use the same result name in multiple Formula blocks.

Something like this - http://prntscr.com/732h8w - is most probably not a good idea for the real world, even for the backtest. This time filter can pass once a day only if there is a tick in one particular second. But what if no tick comes in that second? I will suggest to use wider time period.

The alternative is to use the timer event, which will work on live, but because of technical reasons this event can't be backtested.