NeoTrader wrote:Hi Steve,

me again...

Still in the Process of making the documentation and getting to grip with your Shell EA
I tumbled over something that I think you should look at.

ModifyOrder()
Your ModifyOrder() Function never reports back if the modify was successful or not...it only creates an Error Report.
This means that SendSingleTrade() can create an order and if the crim is an ECN and the ModifyOrder fails you would have an open Order without SL/TP set.

Wouldn't it be better to define ModifyOrder as bool and send a true/false back if it was successful or has failed? And repeat the Modify Process till it succeeds?

Or did I miss something?


happy trading,

NeoTrader

-

SteveHopwood wrote:Welcome to the warped and twisted world of Crapql4 order sending - my world.

What if the ordermodify continues to fail? What if continued, unlimited attempts to modify the order sets up unforeseen memory problems that cause an endless loop, platform freeze or computer crash?

Is this possible? I do not know, but I tell you this: we are relying on a combination of Crapdows os, Empty4 and Crapql4. Is the sort of scenario I describe above so unlikely? And how about all the possible combinations this Trio of Woe and Cataclysmic Crap might throw up that we cannot foresee? No idea what they might be, because nobody has foreseen them. Apart from the cowboys who programmed all this rubbish, who have probably built in quite a lot of stuff deliberately to make watertight code almost impossible to achieve.

Those were the questions that raced through my mind when I contemplated the very same problem you raised, back when Matt first produced the code.

InsertStopLoss/TakeProfit are the functions that deal with the prob. They are both called from within CountOpenTrades and insert said thingies when they should be there but are not. Developers just need to be aware that the functions might need adapting to suit the needs of the system.

if (OrderType() == OP_BUY)
{
stop = CalculateStopLoss(OP_SELL);
}//if (OrderType() == OP_BUY)

if (OrderType() == OP_SELL)
{
stop = CalculateStopLoss(OP_SELL);
}//if (OrderType() == OP_SELL)

NeoTrader wrote:hi Steve

SteveHopwood wrote:Welcome to the warped and twisted world of Crapql4 order sending - my world.

What if the ordermodify continues to fail? What if continued, unlimited attempts to modify the order sets up unforeseen memory problems that cause an endless loop, platform freeze or computer crash?

Is this possible? I do not know, but I tell you this: we are relying on a combination of Crapdows os, Empty4 and Crapql4. Is the sort of scenario I describe above so unlikely? And how about all the possible combinations this Trio of Woe and Cataclysmic Crap might throw up that we cannot foresee? No idea what they might be, because nobody has foreseen them. Apart from the cowboys who programmed all this rubbish, who have probably built in quite a lot of stuff deliberately to make watertight code almost impossible to achieve.

Those were the questions that raced through my mind when I contemplated the very same problem you raised, back when Matt first produced the code.

InsertStopLoss/TakeProfit are the functions that deal with the prob. They are both called from within CountOpenTrades and insert said thingies when they should be there but are not. Developers just need to be aware that the functions might need adapting to suit the needs of the system.

Ok... I understand the problematic...but if the ModifyOrder fails when you call it then the other two Functions will also fail because of the same Problem because all three Functions use the OrderModify Function of Empty4 to complete their task.

By the way I think I found a bloop in your InsertStopLoss() Function in the current ShellEA BareBone

if (OrderType() == OP_BUY)
{
stop = CalculateStopLoss(OP_SELL);
}//if (OrderType() == OP_BUY)

if (OrderType() == OP_SELL)
{
stop = CalculateStopLoss(OP_SELL);
}//if (OrderType() == OP_SELL)

The red selection should be OP_BUY if I'm not wrong (Line1683).



happy trading,

NeoTrader

-

SteveHopwood wrote:They try again at every tick and alert me to a problem. I am happy with this as it is - it ain't bust so I ain't fixin' it.

if (OrderType() == OP_BUY)
{
profit = bid - OrderOpenPrice();
}//if (OrderType() == OP_BUY)

if (OrderType() == OP_SELL)
{
profit = OrderOpenPrice() - ask;
}//if (OrderType() == OP_SELL)

NeoTrader wrote:hi steve,

and again some observations and thoughts...


Function CalculateTradeProfitInPips(int type)
I know that you don't really use this Function actively anywhere in your Code. But it is still there and therefore I thought I check this up with you.

In the call of the Function there is a Function Parameter "type" but you don't use this parameter inside your code.

if (OrderType() == OP_BUY)
{
profit = bid - OrderOpenPrice();
}//if (OrderType() == OP_BUY)

if (OrderType() == OP_SELL)
{
profit = OrderOpenPrice() - ask;
}//if (OrderType() == OP_SELL)

Shouldn't the "type" parameter used here instead of the OrderType() Function?


Function GetSwap()
This Function uses only the current Symbol to get the Swap Values. Wouldn't it be better to use GetSwap(symbol) to be more flexible and also usable in multi-pair EA's?

Thanks in advance,

NeoTrader

-

NeoTrader wrote:Hi Steve,

found another thingy that got some bells ringing.

Function JumpingStopLoss()

Line2007 if (Bid >= sl + ((JumpingStopPips * 2) / factor) )//George{

Line2024 if (Bid <= sl - ((JumpingStopPips * 2) / factor) )//George

Can you tell me why you multiply the JumpingStopPips with 2 here?

Thanks in advance,

happy trading,

NeoTrader

gaheitman wrote:If the JSL is set for 40, it has to move 80 before it jumps 40. It basically locks in half of the move every time we have 2 x JumpingStopPips of room between SL and price.