Of course there is a similar routine on the sell side
The counterreste is to reste the counter on the sellside
Anyway Counter could be used (abused) like that, no?
Of course there is a similar routine on the sell side
The counterreste is to reste the counter on the sellside
Anyway Counter could be used (abused) like that, no?
Thanks
I went back to an older version. And redid most of the changes
So far so good
No stack overflow yet
I have a stack overflow problem, so the EA wont run!
Any ideas why?
The EA has about 200blocks, is that too much?
I also noticed that the block numbers have been getting bigger an bigger, and bigger, last block I added was 100425!
Normalize Block ID dows not seem to work
Please help
I want to know if the following setup would give the following result
What I want to achieve:
Each Time A certain trading condition is true the EA should buy once per bar. However the number of times the Buy should get executed is limited to 4
So in other words the routine only adds maximum of 4 trades when the buy conditions are true, even if the condition stays true for many more bars
When the market reverses it then resets the counter for the opposite trades, so when buy condition is true it reset the sellcounter
Would this look like this in fxdreema magic?

......
counterbuy.png
I checked iexposure calculates based on weighted, instead of count it use lotszies
which makes more sens as the number of trades is not relevant (unless they are all the same lotsize)
if you cahnge it for weighted it would give you the BE price of all open buy trades, which is very useful when hedging and minimizing account loss
let us know whether you change it or add another option
thansk
First observation
I retrieved the average price of all open buy orders adn all open sell orders
when I compare to iExposure it does not give the same average price
What is the difference in the calculations?
Thanks
I will have a look and start experimenting
Cheers
Okay I will wait for the release
Ok
So I set block numbers manually
So the toplevel block number of the part I wnat to run first is lower then the parts that comes after
I imagine only the toplevel block is important, as everything chainlinked after will run automatically once the first toplevel runs, right?
Thanks
I will try that
should ahve thought of that, darn 
I have 3 different trade groups (which are assigned different groups by an Fxdreema EA and I add manual trades sometimes
I want to have group 1 and manual trades to be dandled by Takeprofit routine 1
and group 3 by takeprofit routine 2
and the group 2 trades by takeprofit routine 3
Ok so it is easy to have group 2 and 3 assigned to a certain TP regime, I just plug in their number in the exsiting system
In the current system, I would ahve to duplicate the TP routines in order to have one that treats manual and another (an exact copy) to handle group 1
So my question is, is there any way I can assign a group number to manual trades?
that way I dont have to duplicate code, even though it is easy enough to do
Thanks
What is the best way to assure that my closure routine is executed before my new trade routine?
I prefer not to chain link them.
Any suggestions?
When I export to mq4 yeseterday and this morning
I suddenly have to correct a mistake in metaeditor by hand
I have to replace
#import "kernel32.dll"
with
#import "kernel32.dll"
bool SleepEx(int ms, bool bAlertable);
#import
to get it to work again
before no issues
did I change something?
Yep seems to be fine now
I will confirm again at the end of day
thanks
any idea for a timeline, to see if I can wait
How would I go about retrieving the highest open price from a group of buy orders?
And how would I retrieve the average open price for all these orders, balanced out for lotsize
Thanks
It is probably the same issue as the once per bar issue
Just reminding you as you have lots to think about
Cheers
Not working correctly
It just keep giving me a message on every tick instead every n bars
The option to look through the mq4 code has dissapeared which is pity for trouble shooting
I think that is normal
when you change timeframe it is as if you remove and reattach the EA
so first it removes the objects and then recreates them as it reinitializes the EA