Posts made by jstap

@xyon126 Thank you very much, am sure this will help a lot.

I will put it into practice now and see where it gets me.

@xyon126: Hi xyon thank you for your info, I am sure you are correct that there is a conflict in the following link everything seems to work but I cannot add a pending condition to on tick, if I do then all buttons stop working.
Latest version

I have looked at your posts but you have a lot and I didn't see anything that may correct this, (is quite possible that I missed what I needed).

What did you mean by everything is under what to do? My understanding is that in general:

1. Button is created in on INIT
2. If button is pressed the state changes
3. In a condition block you can use the changed state to do something, (in either CHART or TICK)
4. once something is done you can set the button back to it's original state

This is what I think the EA is doing, I may be wrong, if you have any ideas of how to get this working better I would be glad of the advice.

After a couple of days of testing different sections of this project I have found the problem, although this still doesn't work on live/demo when everything is in the on tick area, it does when in the on chart area.

The answer was quite simple, remove/delete the condition block under the mouse clicked on object block, it seems that having mouse click and a condition basically trying to do the same thing caused problems.

@l-andorrà Thank you

Back test project link
No back test project link

In the "back test project" link, is my latest project but although all works properly in back test it doesn't in live/demo, when the button to place trade is pressed nothing happens.

In the "no back test project" link, is my latest project that will only work on live/demo but it doesn't, like the other when the button to place trade is pressed nothing happens.

Can anyone see that I have done somthing wrong with these? Maybe someone has an idea of what I can do to get them working? Thank you

@jstap Something else I figured out, if the top block is comma separated e.g 1,2, then the connected trees can contain both group 1 & 2 providing it doesn't conflict.

@l-andorrà No problem:)

@l-andorrà So I jumped the gun in blaming my computer, this was not the problem, I found the problem though.

If your 1st block (No trade in this case) has an empty group number, and you 2nd and 3rd block (buy and pending sell, in this case) have a group number.
Then the EA will generate multiple trades, if all 3 blocks have the same number then it works as expected.

@l-andorrà So you learn new every day, so they say, well today I did.
It turns out that having too much happening with my computer caused the group problems.
Thank you, I think I can now get all working

@l-andorrà Interesting, I will ty again now, it is possible I had too much happening with my computer and it caused the problem.

HI l'andorra, thanks for the reply, I have tried to add different groups but hundreds of trades are added so EA stops working.
I even made a simple version which you can see in the link, but it also generated hundreds of trades.
test project
If I am doing something wrong with this then advice is appreciated and maybe I can get it working.

project link

In this project every time a sell is created a pending buy is placed, this is then deleted if within a set distance of the already running buy trade, once this is working I will use as a condition to prevent placing trade. Without the (check distance--delete pending) the EA works as expected, but some trades are generated too close, with this condition all buy pending's are deleted straight away, regardless of the pips from existing trade.

Any help would be much appreciated.

@jstap Ignore me, moved it back into the on tick area, made true in inputs and all worked.

On this project, when the trade button is pressed to stop trading, trailing stop also stops. Any idea why?

link to project: https://fxdreema.com/shared/MhsNoApFc)

@princeclaw Thank you, just saw your reply, the link is within the "link text" wording.

@l-andorrà Logically this would make sense , but when I have tried this it still continued to generate more than one order (that many the back test would crash), as you can see in the latest version I have added resetting the pass once block when trade closed or pending deleted seams to wor best.

@jstap link text

An update from me.

1. My computer doesn't like to run a back test on per tick.
2. For some reason back test had to run for some time to generate sells.
3. Now I have added an option to check if L1 & H1 is a bull or bear candle it now generates buys and sells, (I assume before when it tried to generate order, it failed due to SL & EN being on the wrong side for weather it tried to generate a buy or sell).

link text

This is the start of a multi conformation EA, on back test it places one pending buy, no sells and it doesn't place another buy once the 1'st is deleted. I don't think I have set this up wrong but maybe I have, any help on why this doesn't place a pending order at every previous L1 & H1 is much appreciated.

@l-andorrà Thank you, this loop is very important to me, it will allow the EA to confirm whether pair is in a place of continuation of structure or needs break of structure, confirm whether the fibo lines up with entrance candle and so the TP is in the correct place.

I take it there is no chance of fxdreema inserting another block for loop with ID?
If I knew how to code I could probably create, I cant, I have someone that can create custom indicators so could probably handle this but he has no idea of how to start.

@l-andorrà So basically1st loop looks back finds indicator 1st blue buffer, ID is saved to V1, V1+1 is copied to V2, 2nd loop uses V2 to find indicator 2nd blue buffer ID and saves it to V3.

This means every time the buffer appears the previous buffer ID will move down the list, and this is repeatable for as many buffer positions as wanted.