Only about making much money, requesting EAs and myself | Page 5 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

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

Attachments: Only about making much money, requesting EAs and myself
Exit Attachments

Only about making much money, requesting EAs and myself

  • #81
  • Sep 3, 2018 11:32am Sep 3, 2018 11:32am
Typical situation: the price is in the 61-100 range...and H4 TDI down....
You see: the later the entries...the more worse! I would take only 3!
And I would limit the entries to a minimum of X points distance to the 100 level....so we haven t this situation like in the picture!
Attached Image (click to enlarge)
Click to Enlarge Name: Screenshot1.png Size: 52 KB
Vucking good EA coder... https://t.ly/AZjRM
  • #82
  • Sep 3, 2018 11:42am Sep 3, 2018 11:42am
Quoting reteid2222
{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...
So what is the current TF? I has to be max M5 if you filter with M15!
Vucking good EA coder... https://t.ly/AZjRM
  • #83
  • Sep 3, 2018 12:20pm Sep 3, 2018 12:20pm
Quoting Nicholishen
{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.
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:

  1. real MTF without peaking into future (search for my earlier posts at MTF threads)
  2. want other types of inputs for the indicators, you can only use them on the OHLC candles (what about other inputs like Heiken Ashi, ABP, Kagi etc.) (as far as i know only v2boni has added some basic features in his TDI)
  3. combine your indicators to something new, e.g. RSIOnMA

Since the TO don't have posted sources to analyze, i would assume she/he has reasons for using the own libs.

Quoting Nicholishen
{quote}Also, ALL classes for MQL programs should inherit CObject
Sorry, thats rubbish.

Let's have a look at the class comment of CObject:
//+------------------------------------------------------------------+
//| Class CObject. |
//| Purpose: Base class for storing elements. |
//+------------------------------------------------------------------+

If you want to store and/or compare instances it will be best practice to do so. There are also original classes from meta that not derived from CObject.
  • #84
  • Sep 3, 2018 1:16pm Sep 3, 2018 1:16pm
Quoting JensItzig
{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 indicators
ONE reason I recoded the indicator classes new...thank you for the answer...
Vucking good EA coder... https://t.ly/AZjRM
  • #85
  • Sep 3, 2018 3:40pm Sep 3, 2018 3:40pm
Quoting reteid2222
{quote} ONE reason I recoded the indicator classes new...thank you for the answer...
You are welcome. I don’t know any of your work and also don’t know anything about your intentions when rewriting stuff.
I only disagree with the kind of general discussion here, even when I take into account that you call yourself such a good programmer (maybe you are maybe not).Time will tell us what’s the truth.

I‘m Personal believe that you wasting time by searching a profitable strategy here. The language mql is only good for tools (that’s why I only programming tools these days). For complex strategies there is missing to much here in MT4 (multithreading etc.) and even when you use DLL the limitation is the call of them from MT4 or the limitation by processing incoming data from the DLL.

I wish you all the best for your quest and will watch silently from now on.
  • #86
  • Edited 10:09pm Sep 3, 2018 7:28pm | Edited 10:09pm
Quoting JensItzig
{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...
Well, I suppose we are all entitled to our opinions... Some people may not be able to use the classes for MTF, but there's not a single reason why they couldn't be used for such a purpose given that they're wrappers for the same low level functions you're using. So to address your points directly:

  1. real MTF without peaking into future (search for my earlier posts at MTF threads)

    1. 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.



  2. want other types of inputs for the indicators, you can only use them on the OHLC candles (what about other inputs like Heiken Ashi, ABP, Kagi etc.) (as far as i know only v2boni has added some basic features in his TDI)

    1. False. They work on any chart because they wrap the built-ins.



  3. combine your indicators to something new, e.g. RSIOnMA

    1. 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.



  4. There are also original classes from meta that not derived from CObject.

    1. 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.



  • #87
  • Sep 3, 2018 11:22pm Sep 3, 2018 11:22pm
Quoting reteid2222
{quote} So what is the current TF? I has to be max M5 if you filter with M15!
I am a useless old man I cannot even understand 5% of what's posted here.
I don't even know how to ask for help to automate my method. Anyway just pm you. Forgive my Stupidity.
Hehehe.
  • #88
  • Sep 3, 2018 11:24pm Sep 3, 2018 11:24pm
Quoting Nicholishen
1. 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.
Then please search in the forum when you don't know what i'm telling in this context.

Quoting Nicholishen
2. False. They work on any chart because they wrap the built-ins.
False! Look at this the yellow MA50 line is wrong when using the build-in.

Attached Image (click to enlarge)
Click to Enlarge Name: MA_with_Bars.png Size: 61 KB
Attached Image (click to enlarge)
Click to Enlarge Name: MA_with_HABars.png Size: 61 KB


Quoting Nicholishen
3. 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.
Under performance points (but this is always an issue due the bad MT implementation itself) i can aggree a bit. But when i want to give the customer to build up own indicators by simply combine them, then i have to. And if the several parts of the combined indicators using the same base (e.g. MA of something) then i want to have the access to the same source of computation.

Quoting Nicholishen
4. 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.
Then you don't know them all. e.g. CCanvas isn't inherited from it
  • #89
  • Sep 3, 2018 11:44pm Sep 3, 2018 11:44pm
Wow 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.

Hehe
  • #90
  • Edited 1:14am Sep 4, 2018 12:45am | Edited 1:14am
Quote
Then please search in the forum when you don't know what i'm telling in this context.
I'm not going to bother going through all of your posts trying to figure how you've redefined MTF. All 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.
  • #91
  • Sep 4, 2018 2:00am Sep 4, 2018 2:00am
Quoting Nicholishen
I'm not going to bother going through all of your posts trying to figure how you've redefined MTF.
For the lazy ones - https://www.forexfactory.com/showthr...91#post8671091

Quoting Nicholishen
All 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.
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 to show heiken ashi, then the calculation are correct when on the showed TF. Since offline charts are more an accident by MT and also removed in MT5 i don't see this as solution and don't want a customer guide through the silly process of creating offline charts + the need to have 2 charts open only to view the same data in other representation.

For me the advice to you will be. Stop teaching in that way you have done. Maybe you're a good programmer but you're not able to judge in the way you have done with less to zero knowledge about the intentions of other developers.
  • #92
  • Sep 4, 2018 4:11am Sep 4, 2018 4:11am
Quoting JensItzig
{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...
Obviously 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 is...

I'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.
  • #93
  • Sep 4, 2018 5:31am Sep 4, 2018 5:31am
Quoting Nicholishen
Obviously 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 is
I will ask my teacher to teach this today, that i will be able to follow your genius brain.

Quoting Nicholishen
I'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.
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. When i look at your posted stuff i don't see any genius work. But congrats you know how to avoid implement own sorting, are able to use the word wrapper, know what a repo is and can bash others work. When you think here only childs playing then go back to your google campus and talk to your equals. Last but not least welcome to my ignore list.
  • #94
  • Sep 4, 2018 11:13am Sep 4, 2018 11:13am
Quoting JensItzig
{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...
That s what I wrote in my two examples...you simply have to go one candle back in the higher TF.....look at my two indicators....
Vucking good EA coder... https://t.ly/AZjRM
  • #95
  • Sep 4, 2018 11:17am Sep 4, 2018 11:17am
Quoting JensItzig
{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....
HAHA... Ok buddy. Thanks. Again, just a quick recap. I originally commented with some helpful advice for OP. Then you showed up to sell your agenda of some nonsense about how you think STL indicator wrappers aren't appropriate for your made up edge cases. In the real world we call that a strawman argument; you injected yourself into the conversation with an argument unrelated to the topic at hand so you could "knock it down" and pretend like you had something truly profound to share. So there I was helping OP on the topic of apples and you come along SCREAMING about oranges.

So I'm not bashing anyone's work... I'm bashing your ficticious made-up argument. You don't seem to know what a wrapper is because you keep making wrong assertions about what it should do and why you can't use it.
  • #96
  • Sep 4, 2018 11:21am Sep 4, 2018 11:21am
Quoting genghistar
Wow 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. Hehe
No...build in indicators like rsi doesn t repaint AFTER closed candles...and are ok...simply use them...
Vucking good EA coder... https://t.ly/AZjRM
  • #97
  • Sep 4, 2018 11:42pm Sep 4, 2018 11:42pm
Quoting Bhindabrar
It 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}
Still I m interested....just show me here results and trades....
Vucking good EA coder... https://t.ly/AZjRM
  • #98
  • Sep 14, 2018 3:10pm Sep 14, 2018 3:10pm
Simply H4 trading on closed candles
Buy: EMA 9 cross EMA 13 up and candle closes over SMA 300
SL: Trailing low last 20 candles
TP: EMA 9 cross EMA 13 dn

Sell: Vice versa

Profitable on AUDUSD, CADJPY, EURUSD,....searching for someone who like to create the optimized set files for 28 pairs and results for the last 2 years....
We can publish the settings for the EMAs and SMA here...
Interest: send email per pm and get link to podio workgroup
Attached Image (click to enlarge)
Click to Enlarge Name: Screenshot1.png Size: 36 KB
Vucking good EA coder... https://t.ly/AZjRM
  • #99
  • Edited Sep 15, 2018 2:24am Sep 14, 2018 4:19pm | Edited Sep 15, 2018 2:24am
Alternative to last post:
This version is running till 2018.10.30 00:00...and can be backtested from 2017 to 2018/7 ANY time later!
People who send me the optimized H4 files for all 28 pairs for 2017 and first 8 months 2018 get the unlimited version...
My work against your work...
Naming of filenames:
The secret of WinUndecor - EURUSD - H4 - 2017-2018-07.set
The same the other ones please...letz go!
Attached Image
Attached File(s)
File Type: ex4 The secret of WinUndecor V1.00 - Forex EA - V5.02.ex4   235 KB | 397 downloads
Vucking good EA coder... https://t.ly/AZjRM
  • #100
  • Sep 17, 2018 1:14pm Sep 17, 2018 1:14pm
"Sultans of Trade":
1.)First of all, we are waiting for the SuperTrend indicator to turn into a GREEN color
2) The candle of the interval at which the trade takes place is ABOVE the SuperTrend indicator and is colored GREEN
3) The AO indicator is colored green (its histogram)
4) The green line of the established ADX indicator with period 14 crossed its RED line from the bottom up
5) The dashed line of the QQE indicator (10) is under its red line.
i found this and it looks very good...what do you think?
Attached Image
Attached File(s)
File Type: mq4 QQESimple.mq4   6 KB | 370 downloads
File Type: mq4 SuperTrend2.mq4   3 KB | 370 downloads
Vucking good EA coder... https://t.ly/AZjRM
0 traders viewing now