Vucking good EA coder... https://t.ly/AZjRM
#14 All Time Return:
406.2%
Making money on GPB/JPY only 35 replies
Haikanoz Trading Journal/Journey (Privately for Myself Only) 12 replies
Converting our BAD EAs to stable profit making systems 1 reply
Making Too Much Money with a Broker? 14 replies
Journal Factory posters - how much money are you making? 17 replies
Disliked{quote} ENTRY: price reached FOR BUYS61, FOR SELL R61 price close above R61, below S61 TDI angle >50 for buy, <50 for sell FOR current TF other timeframe except daily must be in agreement...so for M15 the TDI from M30 to H4 is pointing up=angle>0 for buy and vice versa EA will enter at the high of previous candle (when price closed below S61) for buy at 0.01 lot and vice versa until it reached 0.1 lot Multiple entries up to 11 times from 0.01 to 0.1 trade at 61: simply trade there EXIT SL: FOR BUY S100/FOR SELL R100 TP: half at S38/R38, other half...Ignored
Disliked{quote} Fair enough, but perhaps a better way to look at it is the simplest solution is to implement already existing libraries. For example, there's a ton of code behind the scenes in some of your favorite built in functions, but you don't go attempting to rewrite your own NormalizeDouble function or your own iMA function. Classes are no different. Less code does not make a class more performant by simply having less characters in a text file, so there is no optimization in that.Ignored
Since the TO don't have posted sources to analyze, i would assume she/he has reasons for using the own libs.
Disliked{quote}Also, ALL classes for MQL programs should inherit CObjectIgnored
Disliked{quote}And that's why i also have a bunch of own coded indicators (even the basic one). Without knowing the intention you can't discuss it in that way. You must implement the basic indicators when you will use it in one or more of this scenarios: real MTF without peaking into future (search for my earlier posts at MTF threads) want other types of inputs for the indicatorsIgnored
Disliked{quote} ONE reason I recoded the indicator classes new...thank you for the answer...Ignored
Disliked{quote} Maybe i'm missing the start of that discussion, but in my eyes you can't use the build in classes for indicators, when using MTF stuff. I mentioned this more than once here in the forum. And that's why i also have a bunch of own coded indicators (even the basic one). Without knowing the intention you can't discuss it in that way. You must implement the basic indicators when you will use it in one or more of this scenarios: real MTF without peaking into future (search for my earlier posts at MTF threads) want other types of inputs for the...Ignored
Disliked{quote} So what is the current TF? I has to be max M5 if you filter with M15!Ignored
Disliked1. I have no idea what you consider "real MTF", but MTF isn't rocket-science. MTF is easier with the indicator classes than with the built-ins because they're convenience wrappers to those functions.Ignored
Disliked2. False. They work on any chart because they wrap the built-ins.Ignored
Disliked3. This is a strawman. You would obviously make your custom indicator as an mql-indicator so it would run on the separate indicator thread, and then you'd subclass CIndicator to roll your own wrapper.Ignored
Disliked4. It's for implementing more than just collection storage, granted, 99% of developers don't know how to properly override these methods in order to implement all the advanced features. BTW, all classes in the MQL4 STL inherit CObject.Ignored
QuoteDislikedThen please search in the forum when you don't know what i'm telling in this context.
DislikedI'm not going to bother going through all of your posts trying to figure how you've redefined MTF.Ignored
DislikedAll I can say is that the STL classes aren't some mystical abstraction of an indicator(s). It's a thin wrapper around the built-in functions, so if you're not getting the same results using the classes that you are with the functions then you're doing something wrong.Ignored
Disliked{quote} For the lazy ones - https://www.forexfactory.com/showthr...91#post8671091 {quote} I guess you don't want or even can't understand the problem. The build-in rubbish is getting the inputs from the OHLC data. That is ok until you dont want process data from other TF's than the current visible or you want to compute from other data than the shows OHLC (e.g. the heiken ashi in my picture). Since this is the real problem i can't get correct results from the build-in bullshit. You're for sure correct if you use offline charts...Ignored
DislikedObviously your agenda is to advertise whatever edge case you were able to solve with your custom indicator... it's either that or you don't understand what a wrapper isIgnored
DislikedI'm talking about OP not rewriting function wrappers that already exists in the STL and you're ranting on about stuff that's completely unapplicable to the conversation.Ignored
Disliked{quote} For the lazy ones - https://www.forexfactory.com/showthr...91#post8671091 {quote} I guess you don't want or even can't understand the problem. The build-in rubbish is getting the inputs from the OHLC data. That is ok until you dont want process data from other TF's than the current visible or you want to compute from other data than the shows OHLC (e.g. the heiken ashi in my picture). Since this is the real problem i can't get correct results from the build-in bullshit. You're for sure correct if you use offline charts...Ignored
Disliked{quote} I will ask my teacher to teach this today, that i will be able to follow your genius brain. {quote} And again i hoe you can hear me in your higher spheres. You can't judge about the work by review some code snippets posted here. You came here to bash the work of the TO. Yes, i'm also don't like the kind he/she is glorify his/her work, but that's not a reason to offend. Your first post with the question about the git repo shows your intentions here. I don't know why you think you are better than others, but this is what you try to tell here....Ignored
DislikedWow first time in any platform tech section and 30 min into this thread and a complete cyber noob but now I can understand why all EAs fail.. becos they are all using technical indicators based and applied wrongly. A real eye opener. HeheIgnored
DislikedIt is working only on H1 time frame Rules: Trade only in direction arrow. Buy or sell 1 pip above or below box. Target price 40-60 pips depends by currency pairs, if opposite arrow appear exit trade. stop loss below or above on resistance/support {file}Ignored