Gary, I just had an idea.garyfritz wrote:If risk-based sizing means "calculate the lot size that, given my current SL, would risk X% of my account," then that's the way I **ALWAYS** trade with real money. That's how you implement basic position-sizing strategies like fixed-fractional sizing. If it wasn't supported in an EA, I'd try to fake it with manually-specified lotsizes, but that only works if you know the SL ahead of time.
OK, then I wouldn't see it either.Not a clue Gary. Also, I am not experiencing a problem here but I have a modern machine with lots of memory.
If anybody who's hitting this CPU issue wants to try an experiment: try the attached. I changed it to only delete/recreate the objects if the price changes. I also completely removed the SendLots calculation, since it's a local variable and it never gets accessed after it's calculated. (Steve, am I missing something there??)
No promises since I can't test it, but see if it helps... (and if it works!!)
I declared OldBarsTime as a datetime. I see from CtapMql4 Help that this is, "Its internal representation is a long integer number of 4 bytes.". Bearing in mind that I do not know the difference between an 'integer' and a 'long integer', is it possible that
Code: Select all
if (OpenTrades > 0 && StackDistancePips > 0 && OldBarsTime != iTime(NULL, LowerTimeFrame, 0))
{
LookForStackTradingOpps();
}//if (OpenTrades > 0)
How about trying declaring OldBarsTime as an int instead of a datetime?
