Flying Slope auto-trading EA

[fxshadow]

Does anyone have 1C also.

[moondog]

Fxshadow

Here is what looks like a clean version of 1c.
Anyway check it out.

Moondog

[harry45]

Hi Harry45, can you share the version 1B, I seem to have overwritten mine.

thanks

Here you are

[jiaxingx]

Have anyone use version 1h?

it is not be tested .

[akara]

Thanks Harry, its really in hot demand.

[SteveHopwood]

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.

Not a clue Gary. Also, I am not experiencing a problem here but I have a modern machine with lots of memory.

OK, then I wouldn't see it either.

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!!)

Gary, I just had an idea.

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)

fails because some strange CrapMql4 thingy causes OldBarsTime to be out by a gazillionth of a second and therefore the object deletion/replacing code is actually activated at every tick? I don't know how long it takes CrapMql4 to delete then replace an object, but a fiver says it is a while.

How about trying declaring OldBarsTime as an int instead of a datetime?

[garyfritz]

"long integer" is 32 bits, "integer" is 16 bits. So a "long integer" can hold a bigger number (about 2 billion vs. 65000). But I don't think MQL supports 16-bit integers. An "int" is a 32-bit integer.

I would keep OldBarsTime as a datetime, since that's what iTime returns. Keep the types matched up to give Empty4 the fewest opportunities to screw it up.

Don't worry about OldBarsTime being off by a gazillionth. It's an integer value, counting the seconds since 1/1/1970. It doesn't do gazillionths.

[jiaxingx]

In the function "bool LookForTradeClosure(int ticket)"

if (HtfSlopeTrend == buyhold) return;//Leave open and hope for stack opps

I think that maybe return "false",anyone think that right?

[garyfritz]

Yes, it's a bool function. It should return true or false.

I suspect that MQL defaults to "false" if you don't pass a value, but it's not a good idea to assume. Especially with MQL.

[jiaxingx]

Hi,garyfritz
I see many people use "OOTB setting" for testing , I do not know what the mean of "OOTB",
Is that default setting?
thanks!